| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Don Baccus <dhogaza(at)pacifier(dot)com>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, The Hermit Hacker <scrappy(at)hub(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: AW: ALTER TABLE DROP COLUMN |
| Date: | 2000-10-15 14:12:13 |
| Message-ID: | 200010151412.KAA29277@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> My trial implementation using physical/logical attribute numbers
> isn't so clean as I expected. I'm inclined to restrict my change to
> fix the TODO
> * ALTER TABLE ADD COLUMN to inherited table put column in wrong place
> though it would also introduce a backward compatibility.
> I could live without DROP COLUMN feature though I couldn't
> live without ADD COLUMN feature.
We have a DROP COLUMN option in the FAQ, so I don't see a rush there.
Sounds like we need your fix for add column with inheritance, but I
suppose the 2x fix for DROP COLUMN could be used to add columns too.
--
Bruce Momjian | http://candle.pha.pa.us
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 | KuroiNeko | 2000-10-15 14:29:31 | RE: AW: ALTER TABLE DROP COLUMN |
| Previous Message | Hiroshi Inoue | 2000-10-15 13:56:12 | RE: AW: ALTER TABLE DROP COLUMN |