Skip site navigation (1) Skip section navigation (2)

Re: drop if exists - first piece

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: drop if exists - first piece
Date: 2005-11-18 23:49:03
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I will apply the attached patch tomorrow, barring objection. This covers 
> drop if exists for the following objects:
>   table view index sequence schema type domain conversion

> I have a simple test script as show below, but I am not sure where to 
> put it in the regression tests - add a new one maybe?

New test seems reasonable.

A few other minor comments:

* The NOTICEs should probably not carry an ERRCODE; usually you just
want a notice to go out with the default "not an error" SQLSTATE.

* The "Assert(missing_ok)"s are a waste of code space --- if
ereport(ERROR) ever returned, there would be vast swaths of the backend
that fail, so there's no point in asserting it only here.  They also
make the reader stop to wonder why they are there, which is probably a
bigger objection.

* It's probably not a good idea to assume that "IF" is a safe name for
a parser symbol --- too much risk of collision with other macros.
I'd suggest "IF_P".

			regards, tom lane

In response to


pgsql-patches by date

Next:From: Tom LaneDate: 2005-11-19 00:59:04
Subject: Re: DROP OWNED again
Previous:From: Andrew DunstanDate: 2005-11-18 22:42:36
Subject: drop if exists - first piece

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group