Re: [PATCHES] Inherited Constraints
От | Simon Riggs |
---|---|
Тема | Re: [PATCHES] Inherited Constraints |
Дата | |
Msg-id | 1134082028.2906.1141.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: [PATCHES] Inherited Constraints (Simon Riggs <simon@2ndquadrant.com>) |
Ответы |
Re: [PATCHES] Inherited Constraints
Re: [PATCHES] Inherited Constraints |
Список | pgsql-hackers |
On Thu, 2005-12-08 at 11:10 +0000, Simon Riggs wrote: > 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? Late night hacking again.... ALTER TABLE .... DROP CONSTRAINT .... CASCADE does of course already exist, so the following should cause dependency violation ERRORs: - omitting the CASCADE when attempting to delete parent constraint - attempting to drop the child constraint Best Regards, Simon Riggs
В списке pgsql-hackers по дате отправления: