Re: pgsql: Recast "ONLY" column CHECK constraints as NO INHERIT - Mailing list pgsql-committers

From Thom Brown
Subject Re: pgsql: Recast "ONLY" column CHECK constraints as NO INHERIT
Date
Msg-id CAA-aLv586yBPrUpa9JaJuKwGdJD6JN9-pvA=mGsLJW=PQ5cX8g@mail.gmail.com
Whole thread Raw
In response to pgsql: Recast "ONLY" column CHECK constraints as NO INHERIT  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-committers
On 21 April 2012 03:57, Alvaro Herrera <alvherre@alvh.no-ip.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

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Use fuzzy not exact cost comparison for the final tie-breaker in
Next
From: Peter Eisentraut
Date:
Subject: pgsql: Fix some typos