| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Alvaro Herrera" <alvherre(at)atentus(dot)com> |
| 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 08:13:46 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOGEPOCCAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > 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.
>
> Hmmm...so how does one check if one is a child in an inheritance
> hierarchy?
Actually, more specifically, how does one check that the column being
dropped or renamed appears in none of one's parent tables?
I notice there's no find_all_ancestors() function...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J. R. Nield | 2002-07-05 10:01:40 | Re: Issues Outstanding for Point In Time Recovery (PITR) |
| Previous Message | Christopher Kings-Lynne | 2002-07-05 07:57:44 | DROP COLUMN Progress |