| From: | Keary Suska <hierophant(at)pcisys(dot)net> |
|---|---|
| To: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: drop column |
| Date: | 2001-10-18 18:03:35 |
| Message-ID: | B7F47597.4D3E%hierophant@pcisys.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Unfortunately, Postgres' greatest shortcoming (IMHO) is the inability to
change table definitions much after creation. To effect any column changes
besides DEFAULT clauses and indexing (and a few other options), you have to
drop and re-create the table.
Keary Suska
Esoteritech, Inc.
"Leveraging Open Source for a better Internet"
> From: Peter Pilsl <pilsl(at)goldfisch(dot)at>
> Date: Thu, 18 Oct 2001 10:44:34 +0200
> To: postgres mailinglist <pgsql-general(at)postgresql(dot)org>
> Subject: [GENERAL] drop column
>
> is there a trick to drop a column in a table ? or do I need to
> recreate the table and drop the old one ?
>
> thnx,
> peter
>
> --
> mag. peter pilsl
>
> phone: +43 676 3574035
> fax : +43 676 3546512
> email: pilsl(at)goldfisch(dot)at
> sms : pilsl(at)max(dot)mail(dot)at
>
> pgp-key available
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-10-18 18:05:22 | Re: Large Files? |
| Previous Message | Tom Lane | 2001-10-18 18:01:44 | Re: Getting OID after Insert |