| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp>, "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "PostgreSQL Development" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: ALTER TABLE DROP COLUMN |
| Date: | 2000-06-10 12:43:06 |
| Message-ID: | 3.0.1.32.20000610054306.0115f020@mail.pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 01:14 AM 6/10/00 -0400, Tom Lane wrote:
>Don Baccus <dhogaza(at)pacifier(dot)com> writes:
>> Oracle gives you the choice between the "cheating" fast method(s) and
>> the "real" slow (really slow?) real method.
>
>> So there's at least real world experience by virtue of example by
>> the world's most successful database supplier that user control
>> over "hide the column" and "really delete the column" is valuable.
>
>Sure, but you don't need any help from the database to do "really delete
>the column". SELECT INTO... is enough, and it's not even any slower
>than the implementations under discussion.
>
>So I'm satisfied if we offer the "hide the column" approach.
<shrug> I wouldn't put a "real" drop column at the top of my list
of priorities, but there is something to be said for user convenience.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-06-10 15:39:41 | Re: Current initdb broken. |
| Previous Message | Tom Lane | 2000-06-10 05:14:37 | Re: ALTER TABLE DROP COLUMN |