Re: Problem identifying constraints which should not be inherited - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Problem identifying constraints which should not be inherited
Date
Msg-id 7407.1206021966@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problem identifying constraints which should not be inherited  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Problem identifying constraints which should not be inherited
List pgsql-bugs
Alvaro Herrera <alvherre@commandprompt.com> writes:
> NikhilS escribió:
>> 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.

> No, because you would then feel that the TODO item is completed and not
> provide a patch for the whole problem :-)

More to the point, it takes a capability away from the user without
actually solving the problem we need to solve, namely to guarantee
consistency between parent and child constraints.  You can be sure
that there is someone out there who will complain that we've broken
his application when we disallow this, and we need to be able to
point to some positive benefit we got from it.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #4044: Incorrect RegExp substring Output
Next
From: "Rui Martins"
Date:
Subject: Re: BUG #4044: Incorrect RegExp substring Output