Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
drop if exists
- From: Andrew Dunstan <andrew(at)dunslane(dot)net>
- To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: drop if exists
- Date: Fri, 14 Oct 2005 20:29:43 -0400
- Message-id: <43504D77.6060504@dunslane.net> <text/plain>
From time to time the suggestion crops up of allowing a DROP IF EXISTS ... syntax. This seems not unreasonable, and I just spent a few minutes looking at what might be involved. Especially in the case of a table, view, sequence and index the changes look like they would be very modest indeed, and not enormously greater in the case of a type, domain, conversion and schema.
Is this worth doing? Would it be acceptable? cheers andrew
- Follow-Ups:
- Re: drop if exists
- From: Rod Taylor
- Re: drop if exists
- From: Alvaro Herrera
- Re: drop if exists
- From: David Fetter
- Re: drop if exists
- Prev by Date: Re: slow IN() clause for many cases
- Next by Date: Re: drop if exists
- Previous by thread: PostgreSQL roadmap for 8.2 and beyond.
- Next by thread: Re: drop if exists
- Indexes: