On Wed, 2005-12-07 at 21:24 +0000, Simon Riggs wrote: > Following patch implements record of whether a constraint is inherited > or not, and prevents dropping of inherited constraints.
Patch posted to -patches list. > What it doesn't do: > It doesn't yet prevent dropping the parent constraint, which is wrong, > clearly, but what to do about it? > 1. make dropping a constraint drop all constraints dependent upon it > (without any explicit cascade) > 2. add a new clause to ALTER TABLE .... DROP CONSTRAINT .... CASCADE > > I prefer (1), since it is SQL Standard compliant, easier to remember and > automatic de-inheritance is the natural opposite of the automatic > inheritance process. Comments, please -hackers? Which implementation should I pick (or another)? > Further patch will utilise this new knowledge to reduce the number of > tests made during constraint_exclusion. Best Regards, Simon Riggs ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly