| From: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
|---|---|
| To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: BETWEEN Node & DROP COLUMN |
| Date: | 2002-07-05 06:57:44 |
| Message-ID: | Pine.LNX.4.44.0207050250190.19948-100000@cm-lcon-46-187.cm.vtr.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christopher Kings-Lynne dijo:
> > > 2. What should I do about inheritance? I'm going to implement
> > it, but are
> > > there issues? It will basically drop the column with the same
> > name in all
> > > child tables. Is that correct behaviour?
> >
> > What happens if I drop an inherited column in a child table? Maybe it
> > works, but what happens when I SELECT the column in the parent table?
>
> I don't know? Tom?
>
> Well, what happens if you rename a column in a child table? Same problem?
It merrily renames the column in the child table (I tried it). When
SELECTing the parent, bogus data appears. Looks like a bug to me.
Maybe the ALTER TABLE ... RENAME COLUMN code should check for inherited
columns before renaming them.
--
Alvaro Herrera (<alvherre[a]atentus.com>)
One man's impedance mismatch is another man's layer of abstraction.
(Lincoln Yeoh)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2002-07-05 07:01:26 | Re: BETWEEN Node & DROP COLUMN |
| Previous Message | Christopher Kings-Lynne | 2002-07-05 06:45:58 | Re: BETWEEN Node & DROP COLUMN |