| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Giacomo Cavalieri <giacomo(dot)cavalieri(at)icloud(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Figure out nullability of query parameters |
| Date: | 2025-06-27 15:15:26 |
| Message-ID: | CAKAnmm+aicuaU7cgEuFb_hwWSPirwv6omnFHhPRfwoOvUh-PjA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-06-27 15:31:08 | Re: analyze-in-stages post upgrade questions |
| Previous Message | David G. Johnston | 2025-06-27 14:52:56 | Re: Figure out nullability of query parameters |