From: Peter Eisentraut <peter_e@gmx.net>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: cataloguing NOT NULL constraints
Date: Sat, 09 Jul 2011 21:45:23 +0300
Message-ID: <1310237123.9823.1.camel@vanquo.pezone.net> (raw)
In-Reply-To: <20110707213401.GA27098@alvh.no-ip.org>
References: <20110707213401.GA27098@alvh.no-ip.org>
On tor, 2011-07-07 at 17:34 -0400, Alvaro Herrera wrote:
> The attached patch introduces pg_constraint rows for NOT NULL
> column constraints.
The information schema views check_constraints and table_constraints
currently make up some artificial constraint names for not-null
constraints. I suppose this patch removes the underlying cause for
that, so could you look into updating the information schema as well?
You could probably just remove the separate union branches for not null
and adjust the contype conditions.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter_e@gmx.net, alvherre@commandprompt.com
Subject: Re: cataloguing NOT NULL constraints
In-Reply-To: <1310237123.9823.1.camel@vanquo.pezone.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox