| From: | Jean-Michel POURE <jm(dot)poure(at)freesurf(dot)fr> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>, "Andrew Sullivan" <andrew(at)libertyrms(dot)info>, "PostgreSQL general list" <pgsql-general(at)postgresql(dot)org> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Feature enhancement request : use of libgda in |
| Date: | 2002-02-12 08:57:48 |
| Message-ID: | 200202120857.g1C8vnF22648@www1.translationforge |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Le Mardi 12 Février 2002 07:29, Christopher Kings-Lynne a écrit :
> I can see the utility of CREATE OR REPLACE VIEW, however for me the DROP
> COLUMN is way more useful. I can't begin to express how annoying it is to
> not be able to drop a column. Sooo annoying...
I recieved a mail from Neil Conway. Here it is :
If ALTER TABLE DROP COLUMN is important to you guys, why not use the
existing code for it? Define _DROP_COLUMN_HACK__ and re-compile, it
should work. I think the implementation is pretty messy: you, or
someone from your time, is welcome to improve it, or suggest a better
way to do things. This code is also experimental, so it could
definately do with some testing and QA.
My point is that, for this feature at least, there are certainly things
that you guys can do to increase the likelihood of ALTER TABLE DROP
COLUMN being in the 7.3 release.
Cheers,
Neil Conway
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2002-02-12 10:54:59 | Re: [HACKERS] Feature enhancement request : use of libgda in |
| Previous Message | Holger Marzen | 2002-02-12 08:35:48 | index use again and again |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kovacs Zoltan | 2002-02-12 09:33:58 | alter table drop column status |
| Previous Message | khare | 2002-02-12 07:12:57 | Add free-behind capability for large sequential scans |