Skip site navigation (1) Skip section navigation (2)

Re: cataloguing NOT NULL constraints

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)commandprompt(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 16:14:30
Message-ID: CA+TgmoaJbuai2wiWjYUMsawZQL57wOhP7Kg9q=kkVO8qc97MQQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2011-07-22 16:16:18
Subject: Re: libedit memory stomp is apparently fixed in OS X Lion
Previous:From: Tom LaneDate: 2011-07-22 16:13:14
Subject: Re: Questions and experiences writing a Foreign Data Wrapper

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group