Re: Catalog domain not-null constraints

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: jian he <jian(dot)universality(at)gmail(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>
Subject: Re: Catalog domain not-null constraints
Date: 2024-03-26 07:30:45
Message-ID: 202403260730.cprszamfv5rx@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2024-Mar-25, Dean Rasheed wrote:

> Also (not this patch's fault), psql doesn't seem to offer a way to
> display domain constraint names -- something you need to know to drop
> or alter them. Perhaps \dD+ could be made to do that?

Ooh, I remember we had offered a patch for \d++ to display these
constraint names for tables, but didn't get around to gather consensus
for it. We did gather consensus on *not* wanting \d+ to display them,
but we need *something*. I suppose we should do something symmetrical
for tables and domains. How about \dD++ and \dt++?

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
Bob [Floyd] used to say that he was planning to get a Ph.D. by the "green
stamp method," namely by saving envelopes addressed to him as 'Dr. Floyd'.
After collecting 500 such letters, he mused, a university somewhere in
Arizona would probably grant him a degree. (Don Knuth)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message walther 2024-03-26 07:36:40 Re: Regression tests fail with musl libc because libpq.so can't be loaded
Previous Message Yasuo Honda 2024-03-26 07:21:46 Re: pg_stat_statements and "IN" conditions