| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | AW: Can the backend return more than one error message per PQexec? |
| Date: | 2001-06-07 09:40:22 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368312@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> ERROR: blah blah
> CODE: 12345
> LOCATION: some/file.c line NNN
It might be handy to have the LOCATION in the postmaster log,
or make it something that needs to be explicitly switched on.
I do not think it is of general interest to users (most errors
will result from normal operation, and not bugs that need to be tracked).
Since access to SQLSTATE will become a hot path once savepoints
are available I think that having SQLSTATE up front would be
more convenient.
exec sql insert into blabla values ....;
if (strncmp(sqlca.sqlstate, "23", 2) == 0) // duplicate key value
exec sql update blabla set ... ;
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-06-07 10:00:30 | Re: behavior of ' = NULL' vs. MySQL vs. Standards |
| Previous Message | Zeugswetter Andreas SB | 2001-06-07 08:17:08 | AW: Re: [PATCHES] Fw: Isn't pg_statistic a security hol e - Solution Proposal |