MIME-Version: 1.0
References: <4915B05B-90B6-4CC2-86E7-EF7C1E2E38C9@icloud.com> <CAKFQuwaBXfo1LaUWYkPtZaTOaeua6b2SDmX=PtB0r9cvcNYd+w@mail.gmail.com>
In-Reply-To: <CAKFQuwaBXfo1LaUWYkPtZaTOaeua6b2SDmX=PtB0r9cvcNYd+w@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Fri, 27 Jun 2025 11:15:26 -0400
Message-ID: <CAKAnmm+aicuaU7cgEuFb_hwWSPirwv6omnFHhPRfwoOvUh-PjA@mail.gmail.com>
Subject: Re: Figure out nullability of query parameters
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Giacomo Cavalieri <giacomo.cavalieri@icloud.com>, 
	"pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000f797a406388f270c"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BaicuaU7cgEuFb_hwWSPirwv6omnFHhPRfwoOvUh-PjA%40mail.gmail.com>
Precedence: bulk

--000000000000f797a406388f270c
Content-Type: text/plain; charset="UTF-8"

>
> 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 via
protocol, yes, but constraints seems a whole other level of bother.

Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

--000000000000f797a406388f270c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote gmail_quote_container"><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">It would be really handy to know t=
hat `$1` is being used as a non nullable value</blockquote></div><div><br><=
/div><div>To push back in a different=C2=A0way, how exactly would this be u=
seful?</div><div><br></div><div>The system catalogs=C2=A0are the best place=
 to get all the various information about a relation, including any and all=
 constraints. Data type info via protocol, yes, but constraints seems a who=
le other level of bother.</div><div><br></div><div dir=3D"ltr" class=3D"gma=
il_signature"><div dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><br></=
div><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchydata.com=
" target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterprise Po=
stgres Software Products &amp; Tech Support</div><div><br></div></div></div=
></div>

--000000000000f797a406388f270c--