Re: DROP COLUMN misbehaviour with multiple inheritance

Christopher Kings-Lynne wrote:
> > 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...

I am for it.  Multiple inheritance is more of a mess than a help.  Just
look at C++.  Everyone is moving away from multiple inheritance for that
reason.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073