From: bboett@erm1.u-strasbg.fr
To: pgsql-sql@postgresql.org
Subject: where's ALTER TABLE table DROP [ COLUMN ] column???
Date: Thu, 24 May 2001 00:49:06 +0200
Message-ID: <20010524004906.K12080@erm1.u-strasbg.fr> (raw)
Hello!
just trying to write an upgrade script for my bookkeeping system.... and
noticed that it seems that i can't throw out the legacy stuff
accumulated over time....
as far as i can tell, i can add columns to a table, but can't remove
them later on.....
is this true? any easy way to circumvent this inside the DB, without
destroying the existing tables (the problem: make backup f the existing
table, without the offending column, drop the table, recreate it, feed
it with the backup) if someone has any solution for this, i am taker!
--
ciao bboett
==============================================================
bboett@earthling.net
http://inforezo.u-strasbg.fr/~bboetthttp://erm1.u-strasbg.fr/~bboett
===============================================================
the total amount of intelligence on earth is constant.
human population is growing....
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: bboett@erm1.u-strasbg.fr
Subject: Re: where's ALTER TABLE table DROP [ COLUMN ] column???
In-Reply-To: <20010524004906.K12080@erm1.u-strasbg.fr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox