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

Re: Problem identifying constraints which should not be inherited

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: NikhilS <nikkhils(at)gmail(dot)com>
Cc: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "Chris Fischer" <Chris(dot)Fischer(at)channeladvisor(dot)com>, pgsql-bugs(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Problem identifying constraints which should not be inherited
Date: 2008-03-27 15:24:29
Message-ID: 9795.1206631469@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
NikhilS <nikkhils(at)gmail(dot)com> writes:
> ...
> * Add logic to mark inherited constraints in the children:
> This can be achieved by introducing a new bool "coninherited" attribute in
> pg_constraint. This will be set to true on only those check constraints that
> are added to children via the inheritance mechanism

It probably needs to be a count not a bool.  You can/should use the
handling of inherited attributes as a pattern to follow --- look at
attislocal and attinhcount.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Simon RiggsDate: 2008-03-27 15:44:58
Subject: Re: Patch queue permenent URLs
Previous:From: Bruce MomjianDate: 2008-03-27 15:18:52
Subject: Patch queue permenent URLs

pgsql-bugs by date

Next:From: Eugen.KonkovDate: 2008-03-27 15:51:58
Subject: Extra empty lines PGv8.3.1
Previous:From: Heikki LinnakangasDate: 2008-03-27 11:52:26
Subject: Re: Problem identifying constraints which should not be inherited

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