| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com> |
| Subject: | Re: Catalog domain not-null constraints |
| Date: | 2024-03-14 14:03:07 |
| Message-ID: | 202403141403.r2nkh3vuhpje@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2024-Mar-14, Peter Eisentraut wrote:
> Perhaps it would make sense if we change the ALTER TABLE command to be like
>
> ALTER TABLE t1 ADD IF NOT EXISTS NOT NULL c1
>
> Then the behavior is like one would expect.
>
> For ALTER TABLE, we would reject this command if IF NOT EXISTS is not
> specified. (Since this is mainly for pg_dump, it doesn't really matter for
> usability.) For ALTER DOMAIN, we could accept both variants.
I don't understand why you want to change this behavior, though.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"La victoria es para quien se atreve a estar solo"
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-03-14 14:03:09 | Re: REVOKE FROM warning on grantor |
| Previous Message | Heikki Linnakangas | 2024-03-14 13:32:04 | Re: BitmapHeapScan streaming read user and prelim refactoring |