From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Chatter on DROP SOMETHING IF EXISTS |
Date: | 2007-02-15 21:10:41 |
Message-ID: | 20070215211040.GA19527@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 08, 2007 at 01:54:13PM -0500, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > I'm honestly looking for some practical use of this. We have debated
> > other NOTICE messages over the years, but they at least tell you
> > something you can use after the command.
>
> The objection I had to the original patch (which didn't return a notice)
> was that this seemed actively misleading:
>
> foo=> DROP TABLE IF EXISTS not_there;
> DROP TABLE
> foo=>
>
> I would be satisfied if the returned command tag were something else,
> maybe "NO OPERATION".
"TABLE blah DID NOT EXIST" might be less confusing...
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-02-15 23:03:26 | Short varlena header bit-packing options |
Previous Message | David Fetter | 2007-02-15 20:10:56 | Re: patch adding new regexp functions |