From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)atentus(dot)com>, <hannu(at)tm(dot)ee>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: DROP COLUMN misbehaviour with multiple inheritance |
Date: | 2002-09-14 00:56:32 |
Message-ID: | Pine.LNX.4.44.0209132045290.17056-100000@cm-lcon1-46-187.cm.vtr.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
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)
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2002-09-14 01:01:23 | DROP TABLE... CASCADE weirdness |
Previous Message | Robert E. Bruccoleri | 2002-09-14 00:06:45 | Large PostgreSQL databases |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2002-09-14 03:50:41 | contrib/cube & contrib/seg regression fixes |
Previous Message | Joe Conway | 2002-09-13 22:57:39 | contrib/dblink GRANTs and regression test fix |