From: | Jose Soares <jose(at)sferacarta(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Column ADDing issues |
Date: | 2000-01-28 14:55:58 |
Message-ID: | 3891ADFE.623D2152@sferacarta.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> > > I suggest you be very cautious about messing with ALTER TABLE until you
> > > understand why inheritance makes it such a headache ;-)
> >
> > I'm just trying to get the defaults and constraints working. If
> > inheritance stays broken the way it previously was, it's beyond my
> > powers. But I get the feeling that people rather not alter their tables
> > unless they have *perfect* alter table commands. I don't feel like arguing
> > with them, they'll just have to do without then.
>
> OK, so am I hearing we don't want ALTER TABLE DROP COLUMN without it
> working for inhertance. Is this really the way we want things? May as
> well disable ADD COLUMN too because that doesn't work for inheritance
> either.
>
I think this is not a good idea. Many of us doesn't interest inheritance.
ALTER ADD COLUMN is not complete but it is better than nothing.
> --
> Bruce Momjian | http://www.op.net/~candle
> pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill, Pennsylvania 19026
>
> ************
--
Jose' Soares
Bologna, Italy Jose(at)sferacarta(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-01-28 15:02:32 | Re: [HACKERS] Re: ORDBMS |
Previous Message | The Hermit Hacker | 2000-01-28 14:51:36 | Re: ORDBMS |