| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| 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-16 06:01:14 |
| Message-ID: | 11036.1171605674@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> On Thu, Feb 08, 2007 at 01:54:13PM -0500, Tom Lane wrote:
>> I would be satisfied if the returned command tag were something else,
>> maybe "NO OPERATION".
> "TABLE blah DID NOT EXIST" might be less confusing...
You're confusing a command tag with a notice. In the first place,
we shouldn't assume that applications are ready to deal with
indefinitely long command tags (the backend itself doesn't think they
can be longer than 64 bytes); in the second place, they should be
constant strings for the most part so that simple strcmp()s suffice
to see what happened. Command tags are meant for programs to deal
with, more than humans.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Drake | 2007-02-16 07:02:33 | Re: patch adding new regexp functions |
| Previous Message | Yoshiyuki Asaba | 2007-02-16 05:09:41 | Re: pg_restore fails with a custom backup file |