From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: cataloguing NOT NULL constraints |
Date: | 2011-07-22 20:39:03 |
Message-ID: | 1311367030-sup-9426@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of vie jul 22 12:14:30 -0400 2011:
> On Thu, Jul 21, 2011 at 7:51 PM, Alvaro Herrera
> <alvherre(at)commandprompt(dot)com> wrote:
> >> I think that there probably ought to be a way to display the NOT NULL
> >> constraint names (perhaps through \d+). For example, if you're
> >> planning to support NOT VALID on top of this in the future, then there
> >> needs to be a way to get the constraint's name to validate it.
> >
> > Absolutely true. Another thing that needs to be done here is to let the
> > ALTER TABLE and ALTER DOMAIN commands use the constraint names; right
> > now, they simply let you add the constraint but not specify the name.
> > That should probably be revisited.
>
> That, at least, seems like something that should be fixed before commit.
Hmm, which point, Dean's or mine? Dean was saying that the name should
be displayed by some flavor of \d; mine was that we need a command such
as
ALTER TABLE foo ALTER COLUMN bar SET NOT NULL name_of_notnull_constr
where the last bit is what's new.
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2011-07-22 20:40:37 | pgbench --unlogged-tables |
Previous Message | Peter Eisentraut | 2011-07-22 20:35:43 | Re: Deferred partial/expression unique constraints |