| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Well, then you keep your darn columns |
| Date: | 2000-01-24 16:50:21 |
| Message-ID: | 200001241650.LAA18853@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> As a user let me just say that I have been waiting for all the
> 'ALTER TABLE..' commands for a long time (changing constraints would be great
> too!) and it has been mentioned many times that one should not use oids in
> application code. The way I do it at the moment is to copy the table, so I
> think all users are used to losing their oids when remocing a column from a
> table. So while it is certainly better to keep the oids, Peter's code is a
> big improvement on the current situation.
>
What happens if the dropped column is part of an index? Just curious.
--
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 | Henry B. Hotz | 2000-01-24 16:59:57 | Re: [HACKERS] Some notes on optimizer cost estimates |
| Previous Message | Tom Lane | 2000-01-24 16:49:20 | Re: [HACKERS] column aliases |