| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Catalog domain not-null constraints |
| Date: | 2023-11-23 06:56:48 |
| Message-ID: | 9ec24d7b-633d-463a-84c6-7acff769c9e8@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
This patch set applies the explicit catalog representation of not-null
constraints introduced by b0e96f3119 for table constraints also to
domain not-null constraints.
Since there is no inheritance or primary keys etc., this is much simpler
and just applies the existing infrastructure to domains as well. As a
result, domain not-null constraints now appear in the information schema
correctly. Another effect is that you can now use the ALTER DOMAIN ...
ADD/DROP CONSTRAINT syntax for not-null constraints as well. This makes
everything consistent overall.
For the most part, I structured the code so that there are now separate
sibling subroutines for domain check constraints and domain not-null
constraints. This seemed to work out best, but one could also consider
other ways to refactor this.
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Add-tests-for-domain-related-information-schema-v.patch | text/plain | 7.2 KB |
| v1-0002-Catalog-domain-not-null-constraints.patch | text/plain | 24.1 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Smith | 2023-11-23 07:27:04 | Re: GUC names in messages |
| Previous Message | jian he | 2023-11-23 06:55:39 | Re: remaining sql/json patches |