Re: cataloguing NOT NULL constraints

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: cataloguing NOT NULL constraints
Date: 2011-08-06 10:03:41
Message-ID: 1312625021.24721.17.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2011-08-06 at 08:17 +0100, Dean Rasheed wrote:
> The current behaviour is inconsistent - the not-null property of a PK
> is sometimes inherited and sometimes not, depending on whether the PK
> is added at table-creation time or later. So a change in either
> direction is a change to some current behaviour, unless we leave it
> inconsistent, which seems unacceptable.

Yeah, OK, that's wrong then.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-08-06 10:13:58 Re: Reduce WAL logging of INSERT SELECT
Previous Message Peter Eisentraut 2011-08-06 10:03:13 Re: cataloguing NOT NULL constraints