Re: conditional dropping of columns/constraints - Mailing list pgsql-hackers

From Chris Browne
Subject Re: conditional dropping of columns/constraints
Date
Msg-id 874ow0ekt5.fsf@dba2.int.libertyrms.com
Whole thread Raw
In response to conditional dropping of columns/constraints  (Andres Freund <andres@anarazel.de>)
Responses Re: conditional dropping of columns/constraints  (Peter Eisentraut <peter_e@gmx.net>)
Re: conditional dropping of columns/constraints  (Andrew Dunstan <andrew@dunslane.net>)
Re: conditional dropping of columns/constraints  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
robertmhaas@gmail.com (Robert Haas) writes:
> On Mon, May 4, 2009 at 10:10 AM, Andres Freund <andres@anarazel.de> wrote:
>> Would a patch adding 'IF EXISTS' support to:
>> - ALTER TABLE ... DROP COLUMN
>> - ALTER TABLE ... DROP CONSTRAINT
>> possibly be accepted?
>>
>> Having it makes the annoying task of writing/testing of schema-upgrade
>> scripts a bit easier.
>
> Can't speak for the committers, but I've wished for this a time or two myself.

For constraints, it's easy enough to treat that as idempotent; it's no
big deal to drop and re-add a constraint.

For columns, I'd *much* more frequently be interested in  ALTER TABLE ... ADD COLUMN IF NOT EXISTS ...

Note that this is distinctly NOT the same as:  ALTER TABLE ... DROP COLUMN IF EXISTS ...  ALTER TABLE ... ADD COLUMN
...
-- 
(format nil "~S@~S" "cbbrowne" "linuxdatabases.info")
http://linuxdatabases.info/info/lisp.html
Signs of a Klingon Programmer -  10. "A TRUE  Klingon Warrior does not
comment his code!"


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: "could not reattach to shared memory" captured in buildfarm
Next
From: Bernd Helmle
Date:
Subject: bytea vs. pg_dump