| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Dave Cramer <dave(at)fastcrypt(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ambiguous sql states |
| Date: | 2003-08-24 20:46:40 |
| Message-ID: | 28272.1061758000@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Dave Cramer writes:
>> I'm working on identifying various errors in ecpg using sql state and
>> one which is particularly ambiguous is ERRCODE_UNDEFINED_OBJECT for a
>> file which isn't found. This is returned in a number of places. Is it
>> possible to get a set of file specific error codes?
> That error code if for undefined objects, not files that can't be found.
Dave's correct, that's what we're currently using. I'm happy to change
it if someone can suggest an appropriate SQLSTATE (even a category...)
to use instead.
I would however like to know why ecpg cares.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jason Tishler | 2003-08-24 20:55:42 | Re: PostgreSQL 7.4 Beta 1 + SSL + Cygwin |
| Previous Message | Tom Lane | 2003-08-24 20:32:15 | Re: Collation rules and multi-lingual databases |