From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, 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: | 2012-08-04 16:50:58 |
Message-ID: | 20120804165058.GE29773@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 22, 2011 at 12:14:30PM -0400, Robert Haas wrote:
> 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.
I have added a URL of this thread to the TODO list.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Mary F. Masterson | 2012-08-04 19:17:55 | Pgadmin3 v1.14.2 foreign keys |
Previous Message | Bruce Momjian | 2012-08-04 16:43:04 | Re: WIP pgindent replacement |