Re: Problem identifying constraints which should not be inherited

Hi,

On Wed, Mar 19, 2008 at 8:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> NikhilS <nikkhils(at)gmail(dot)com> writes:
> > On Fri, Mar 7, 2008 at 6:37 AM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> >> Added to TODO:
> >> o Require all CHECK constraints to be inherited
>
> > PFA, a small patch attached which should fix this.
>
> If it's a small patch, it's wrong by definition. AFAICS there is no way
> to fix this correctly that doesn't involve catalog changes. The point
> of the TODO is that you have to enforce that the inherited constraint
> sticks around, eg can't be dropped on a child table while it's still
> present on the parent. There are implications for pg_dump too.
>

Ok, I understand. But even then this could patch could be considered even if
it does not solve the TODO completely, no? It atleast disallows ONLY ADD
CONSTRAINT on the parent.

Regards,
Nikhils

--
EnterpriseDB http://www.enterprisedb.com