Re: ADD/DROP CONSTRAINT and inheritance
| От | Tom Lane |
|---|---|
| Тема | Re: ADD/DROP CONSTRAINT and inheritance |
| Дата | |
| Msg-id | 26759.990673193@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | RE: ADD/DROP CONSTRAINT and inheritance ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
| Ответы |
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.
> 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.
regards, tom lane
В списке pgsql-hackers по дате отправления: