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
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-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

Browse pgsql-bugs by date

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

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-03-27 15:44:58 Re: Patch queue permenent URLs
Previous Message Bruce Momjian 2008-03-27 15:18:52 Patch queue permenent URLs