| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)atentus(dot)com> |
| Cc: | <hannu(at)tm(dot)ee>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Date: | 2002-09-20 02:08:00 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOAEFJCEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> That seems right, but the problem I have with it is that the resulting
> state of c.f1 is attisinherited = 1. This means that you cannot drop
> c.f1. It seems to me that we should have this behavior:
Has anyone given much thought as to perhaps we could just drop multiple
inheritance from Postgres? There are people using single inheritance - but
how many actually use multiple inheritance? If we dumped it we could use
the proposed all-child-tables-in-one-relation idea, and everything would
become very easy...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-20 02:27:11 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Previous Message | Christopher Kings-Lynne | 2002-09-20 02:05:06 | Re: Postgres 7.2.2 Segment Error |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-20 02:27:11 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Previous Message | Joe Conway | 2002-09-19 21:58:38 | Re: [GENERAL] Memory Errors... |