Received: from erm1.u-strasbg.fr (erm1.u-strasbg.fr [130.79.74.61]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4NMg2A01667 for ; Wed, 23 May 2001 18:42:02 -0400 (EDT) (envelope-from bboett@erm1.u-strasbg.fr) Received: by erm1.u-strasbg.fr (Postfix, from userid 501) id 029875E36; Thu, 24 May 2001 00:49:06 +0200 (CEST) Date: Thu, 24 May 2001 00:49:06 +0200 To: pgsql-sql@postgresql.org Subject: where's ALTER TABLE table DROP [ COLUMN ] column??? Message-ID: <20010524004906.K12080@erm1.u-strasbg.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.3.15i From: bboett@erm1.u-strasbg.fr (Bruno Boettcher) X-Archive-Number: 200105/258 X-Sequence-Number: 3086 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/~bboett http://erm1.u-strasbg.fr/~bboett =============================================================== the total amount of intelligence on earth is constant. human population is growing....