Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Recast "ONLY" column CHECK constraints as NO INHERIT

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: (view raw, whole thread or download thread mbox)
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:


In doc/src/sgml/ref/create_table.sgml:

"A constraint marked with NO INHERIT will not propagate to children tables."



In response to

pgsql-committers by date

Next:From: Peter EisentrautDate: 2012-04-22 16:24:26
Subject: pgsql: Fix some typos
Previous:From: Tom LaneDate: 2012-04-21 04:51:25
Subject: pgsql: Use fuzzy not exact cost comparison for the final tie-breakerin

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group