From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | 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-27 17:52:43 |
Message-ID: | 200001271752.MAA26087@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > 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.
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-01-27 18:05:00 | Re: [HACKERS] CVS problem |
Previous Message | Tom Lane | 2000-01-27 17:52:37 | Re: [SQL] RE: [GENERAL] Problem with SELECT on large negative INT4 |