From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: cataloguing NOT NULL constraints |
Date: | 2023-08-16 10:09:33 |
Message-ID: | c1ce5a9a-6f6d-e0c7-a16b-35ce9d605a84@eisentraut.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I have two small patches that you can integrate into your patch set:
The first just changes the punctuation of "Not-null constraints" in the
psql output to match what the documentation mostly uses.
The second has some changes to ddl.sgml to reflect that not-null
constraints are now named and can be operated on like other constraints.
You might want to read that again to make sure it matches your latest
intentions, but I think it catches all the places that are required to
change.
Attachment | Content-Type | Size |
---|---|---|
0001-fixup-Have-psql-print-the-NOT-NULL-constraints-on-d.patch.nocfbot | text/plain | 28.1 KB |
0002-Update-ddl.sgml-for-named-not-null-constraints.patch.nocfbot | text/plain | 4.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2023-08-16 10:24:33 | Re: Todo: Teach planner to evaluate multiple windows in the optimal order |
Previous Message | Alvaro Herrera | 2023-08-16 10:07:43 | Re: regexp_replace weirdness amounts to a bug? |