Re: DROP COLUMN misbehaviour with multiple inheritance
От | Alvaro Herrera |
---|---|
Тема | Re: DROP COLUMN misbehaviour with multiple inheritance |
Дата | |
Msg-id | Pine.LNX.4.44.0209132045290.17056-100000@cm-lcon1-46-187.cm.vtr.net обсуждение исходный текст |
Ответ на | Re: DROP COLUMN misbehaviour with multiple inheritance (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: DROP COLUMN misbehaviour with multiple inheritance
|
Список | pgsql-hackers |
Tom Lane dijo: > One corner case is that I think we currently allow > > create table p (f1 int); > create table c (f1 int) inherits(p); In this case, c.f1.attisinherited count is 2; thus when I drop f1 from p, it is not dropped from c. Do you have some suggestion on what the name should be? Clearly attisinherited is not appropiate. attinhcount maybe? The patch submitted does what you describe. I'm leaving tomorrow and won't be back until next weekend, so please do the name change yourself if the patch is to be applied. -- Alvaro Herrera (<alvherre[a]atentus.com>) Voy a acabar con todos los humanos / con los humanos yo acabaré voy a acabar con todos / con todos los humanos acabaré (Bender)
В списке pgsql-hackers по дате отправления: