RE: ADD/DROP CONSTRAINT and inheritance
От | Christopher Kings-Lynne |
---|---|
Тема | RE: ADD/DROP CONSTRAINT and inheritance |
Дата | |
Msg-id | ECEHIKNFIMMECLEBJFIGAEKCCAAA.chriskl@familyhealth.com.au обсуждение исходный текст |
Ответ на | Re: ADD/DROP CONSTRAINT and inheritance (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: ADD/DROP CONSTRAINT and inheritance
|
Список | pgsql-hackers |
> "Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes: > > I'm not sure what you mean here, Tom - I meant that the ONLY > keyword could > > be optional. > > The current gram.y code allows either ALTER TABLE foo ONLY or ALTER > TABLE foo* for all forms of ALTER ... with the default interpretation > being the latter. Oops - ok, I didn't notice that...hmmm...maybe I should check my patch for that before Bruce commits it... > > At the moment we have: > > * ADD CONSTRAINT does not propagate > > I doubt you will find anyone who's willing to argue that that's not a > bug --- specifically, AlterTableAddConstraint()'s lack of inheritance > recursion like its siblings have. Feel free to fix it. It was next on my list. However, I don't want to step on Stephan's toes... Chris
В списке pgsql-hackers по дате отправления: