Hi,
> So I don't recommend you try to do this. What is the actual problem
> you are trying to solve? Why do you want the client library to be
> concerned with attnotnull at all?
In general the client library needs to check attnotnull to make sure
that the client is not making a type mistake.
Dear list,
Here's the situation: I want to create a functional API to a Postgresql
database, in such a way that instead of issuing raw SQL commands (SELECT,
INSERT, etc), the client will only invoke functions from this API.
For example, to get all people in the database, the client will invoke
f
