At 15:24 06/04/01 -0400, Sheer El-Showk wrote:
>I'm using what I presume to be the only/most popular JDBC for postgres
>(from http://jdbc.postgresql.org/download; the actual jar is
>jdbc7.0-1.1.jar -- please let me know if there are any others) but am a
>little concerned that its error reporting (via java SQL exceptions) seems
>to use only strings rather then setting the exceptions error code (vendor
>specific or XOPEN standard).
>I need to be able to catch SQLExceptions and convert them to my own,
>application specific exceptions ... I can even do this by parsing a string
>(though I would rather an error code), but I don't know how to reliably
>extract DB errors from the exceptions thrown by the postgres JDBC driver.
>Any suggestions, references or help would be greatly appreciate.
There was discussion about this a few weeks ago. Implementing the codes is
on hold, as this may endup being a feature being added to the main backend
in 7.2. Until then, I'm afraid parsing the strings is the only way.
Tip: In the source, look at the errors.properties file, it's all the JDBC
specific errors returned. Any others are from the backend.
pgsql-jdbc by date
|Next:||From: Peter Mount||Date: 2001-04-10 15:49:56|
|Subject: RE: null to zero?|
|Previous:||From: Doug McNaught||Date: 2001-04-10 06:14:23|
|Subject: Re: [HACKERS] JDBC and Perl compiling problems w/ postgresql-7.1rc4|