Re: cataloguing NOT NULL constraints

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: cataloguing NOT NULL constraints
Date: 2023-08-28 15:44:55
Message-ID: 20230828154455.pfihomnzwqvb4yrz@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2023-Aug-28, Peter Eisentraut wrote:

> It looks like we forgot about domain constraints? For example,
>
> create domain testdomain as int not null;
>
> should create a row in pg_constraint?

Well, at some point I purposefully left them out; they were sufficiently
different from the ones in tables that doing both things at the same
time was not saving any effort. I guess we could try to bake them in
now.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Doing what he did amounts to sticking his fingers under the hood of the
implementation; if he gets his fingers burnt, it's his problem." (Tom Lane)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matthias van de Meent 2023-08-28 15:49:50 Re: Disabling Heap-Only Tuples
Previous Message Melanie Plageman 2023-08-28 15:42:22 Re: Commitfest manager for September