Re: Catalog domain not-null constraints

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>

To: Alvaro Herrera <alvherre@alvh.no-ip.org>

Cc: jian he <jian.universality@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>, vignesh C <vignesh21@gmail.com>, Aleksander Alekseev <aleksander@timescale.com>

Date: 2024-03-18T07:46:28Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix ALTER DOMAIN NOT NULL syntax
- 9895b35cb88e 17.0 landed
Catalog domain not-null constraints
- e5da0fe3c22b 17.0 landed
Add tests for domain-related information schema views
- 9578393bc513 17.0 landed

Attachments

v4-0001-Add-tests-for-domain-related-information-schema-v.patch (text/plain) patch v4-0001
v4-0002-Catalog-domain-not-null-constraints.patch (text/plain) patch v4-0002

Anyway, in order to move this forward, here is an updated patch where 
the ADD CONSTRAINT ... NOT NULL behavior for domains matches the 
idempotent behavior of tables.  This uses the patch that Jian He posted.