> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Michael Glaesemann
> Sent: 14 November 2005 14:54
> To: Andrew Dunstan
> Cc: Patches (PostgreSQL)
> Subject: Re: [PATCHES] drop if exists
>
>
> 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.
Yes, a notice would certainly be nice:
andrew=# drop table blurflx;
ERROR: table "blurflx" does not exist
andrew=# drop table if exists blurflx;
NOTICE: table "blurflx" does not exist
DROP TABLE
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
