From: | Michael Glaesemann <grzm(at)myrealbox(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: drop if exists |
Date: | 2005-11-14 14:53:45 |
Message-ID: | 6B04F21E-BAD7-473C-96F7-3EE349B0515B@myrealbox.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
On Nov 14, 2005, at 23:25 , Andrew Dunstan wrote:
>
> Ther attached patch is for comment. It implements "drop if exists"
> as has recently been discussed. Illustration:
Nifty! Thanks for working this up, Andrew!
> andrew=# drop table blurflx;
> ERROR: table "blurflx" does not exist
> andrew=# drop table if exists blurflx;
> DROP TABLE
I'm not sure what other DBMS' return in this situation (and kindly
ignore this suggestion if it's specified or otherwise determined),
but perhaps the output could be TABLE "blurlx" DOES NOT EXIST
(without the ERROR) or something more informative, rather than DROP
TABLE. It reminds me of the old behavior of outputting COMMIT even in
the case of transaction failure. I find the current behavior of
outputting ROLLBACK in the case of transaction failure more useful.
Michael Glaesemann
grzm myrealbox com
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2005-11-14 15:12:04 | Re: drop if exists |
Previous Message | Andrew Dunstan | 2005-11-14 14:25:49 | drop if exists |