Re: Figure out nullability of query parameters

> > It would be really handy to know that `$1` is being used as a non nullable > value To push back in a different way, how exactly would this be useful? The system catalogs are the best place to get all the various information about a relation, including any and all constraints. Data type info

Re: Figure out nullability of query parameters

On Friday, June 27, 2025, Giacomo Cavalieri wrote: > > It would be really handy to know that `$1` is being used as a non nullable > value, while `$2` could actually be null. Can this already be achieve > today, or would there be a way to surface this kind of information for > query parameters in

Re: Figure out nullability of query parameters

Hi, I have no idea how/if this is possible using the query protocol but I would try to parse the INSERT statement to get the table and columns names and then look up whether they are nullable in the information schema ( https://www.postgresql.org/docs/current/infoschema-columns.html) Petr On Fri,

Figure out nullability of query parameters

Hello! I’m Giacomo, I’m the maintainer of , a tool that can generate type safe bindings to run and decode the results of Postgres queries. It does that by implementing the extended query protocol, which, among other things, returns the OIDs of the q