Re: cataloguing NOT NULL constraints

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
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 07:23:28
Message-ID: CAEZATCXOzq8vqyHeiEX93MBVptASj2tWiCXjK7-Ju125x3x_wQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 6 August 2011 08:17, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> 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.
>

Oops, that should have been "depending on whether the PK is defined
before or after the inheritance is set up".

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2011-08-06 08:23:30 Re: Reduce WAL logging of INSERT SELECT
Previous Message Dean Rasheed 2011-08-06 07:17:58 Re: cataloguing NOT NULL constraints