| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "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-20 02:55:10 |
| Message-ID: | GNELIHDDFBOCMGBFGEFOAEFKCEAA.chriskl@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > > I am for it. Multiple inheritance is more of a mess than a help.
> >
> > I'm not agin it ... but if that's the lay of the land then we have
> > no need to apply a last-minute catalog reformatting to fix a
> > multiple-inheritance bug. This patch is off the "must fix for 7.3"
> > list, no?
Multiple inheritance patches should go in for 7.3, since we support multiple
inheritance in 7.3. However, I think thought should be put into removing
multiple inheritance in 7.4 - after a user survey perhaps. If removing
multiple inheritance means we can have perfece, indexable single inheritance
then I think it's worth it. Unless the spec calls for multiple inheritance
of course.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vince Vielhaber | 2002-09-20 03:00:26 | Re: Beta2 on Friday Morning (Was: Re: Open 7.3 items) |
| Previous Message | Bruce Momjian | 2002-09-20 02:52:15 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-20 03:15:11 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Previous Message | Bruce Momjian | 2002-09-20 02:52:15 | Re: DROP COLUMN misbehaviour with multiple inheritance |