From: | Thom Brown <thom(at)linux(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Recast "ONLY" column CHECK constraints as NO INHERIT |
Date: | 2012-04-21 08:17:21 |
Message-ID: | CAA-aLv586yBPrUpa9JaJuKwGdJD6JN9-pvA=mGsLJW=PQ5cX8g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
On 21 April 2012 03:57, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>
> Recast "ONLY" column CHECK constraints as NO INHERIT
>
> The original syntax wasn't universally loved, and it didn't allow its
> usage in CREATE TABLE, only ALTER TABLE. It now works everywhere, and
> it also allows using ALTER TABLE ONLY to add an uninherited CHECK
> constraint, per discussion.
>
> The pg_constraint column has accordingly been renamed connoinherit.
>
> This commit partly reverts some of the changes in
> 61d81bd28dbec65a6b144e0cd3d0bfe25913c3ac, particularly some pg_dump and
> psql bits, because now pg_get_constraintdef includes the necessary NO
> INHERIT within the constraint definition.
A couple typos:
In doc/src/sgml/ref/alter_table.sgml:
s/explicitely/explicitly/
In doc/src/sgml/ref/create_table.sgml:
"A constraint marked with NO INHERIT will not propagate to children tables."
s/children/child/
--
Thom
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-04-22 16:24:26 | pgsql: Fix some typos |
Previous Message | Tom Lane | 2012-04-21 04:51:25 | pgsql: Use fuzzy not exact cost comparison for the final tie-breaker in |