| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: cataloguing NOT NULL constraints |
| Date: | 2022-09-20 10:53:02 |
| Message-ID: | 20220920105302.dyy2na6zfji4ded3@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Sep-19, Isaac Morland wrote:
> I thought I saw some discussion about the SQL standard saying that there is
> a difference between putting NOT NULL in a column definition, and CHECK
> (column_name NOT NULL). So if we're going to take this seriously,
Was it Peter E.'s reply to this thread?
https://postgr.es/m/bac841ed-b86d-e3c2-030d-02a3db067307@enterprisedb.com
because if it wasn't there, then I would like to know what you source
is.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end." (2nd Commandment for C programmers)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2022-09-20 10:56:19 | Re: cataloguing NOT NULL constraints |
| Previous Message | Alvaro Herrera | 2022-09-20 10:51:09 | Re: cataloguing NOT NULL constraints |