From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Rod Taylor <pg(at)rbt(dot)ca> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: drop if exists |
Date: | 2005-10-15 14:12:45 |
Message-ID: | 43510E5D.8080406@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rod Taylor wrote:
>On Fri, 2005-10-14 at 20:29 -0400, Andrew Dunstan wrote:
>
>
>> 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.
>>
>>
>
>I would rather have a 'rollback or release savepoint' command which
>would rollback to the savepoint if there was an error or release it
>otherwise.
>
>This way any command or combination of commands could be aborted or
>continued as a group in a statically defined script.
>
>
>
I don't see that they are mutually exclusive, although one could achieve
the effect this way.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-10-15 14:22:01 | Re: drop if exists |
Previous Message | Martijn van Oosterhout | 2005-10-15 14:04:52 | Re: A costing analysis tool |