Re: ADD/DROP CONSTRAINT and inheritance
От | Tom Lane |
---|---|
Тема | Re: ADD/DROP CONSTRAINT and inheritance |
Дата | |
Msg-id | 16062.990640521@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: ADD/DROP CONSTRAINT and inheritance (Stephan Szabo <sszabo@megazone23.bigpanda.com>) |
Ответы |
RE: ADD/DROP CONSTRAINT and inheritance
|
Список | pgsql-hackers |
Stephan Szabo <sszabo@megazone23.bigpanda.com> writes: > On Wed, 23 May 2001, Christopher Kings-Lynne wrote: >> For the add/drop constraint clauses would it be an idea to change the syntax >> to: >> >> ALTER TABLE [ ONLY ] x ADD CONSTRAINT x; >> ALTER TABLE [ ONLY ] x DROP CONSTRAINT x; If the patch is coded in the same style as the existing ALTER code then this will happen automatically. Are you looking at current development tip as the comparison point for your changes? > A related question is whether or not you can drop a constraint on a > subtable that's inherited from a parent. There is the question of whether it's a good idea to allow a constraint to exist on a parent but not on its subtables. Seems like a bad idea to me. But as long as the default is to propagate these changes, I'm not really eager to prohibit DBAs from doing the other. Who's to say what's a misuse of inheritance and what's not... regards, tom lane
В списке pgsql-hackers по дате отправления: