This is on the TODO list for the backend. As a post a couple of days
ago stated, when the backend has error code support, it will also be
added to JDBC. Until then....
Peter Wiley wrote:
> It's been mentioned before, but a set of error numbers for database errors
> would make trapping exceptions and dealing with them gracefully a LOT
> simpler. I have java code that runs against Oracle, Informix, PostgreSQL,
> MS SQL Server and Cloudscape. All(?) the others have an error code as well
> as an error message and it's a lot easier to get the error code.
> Of course, they all have *different* error codes for the same error (ie
> primary key violation). Nothing is ever simple.
> Peter Wiley
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
In response to
pgsql-hackers by date
|Next:||From: Carfield Yim||Date: 2001-08-27 17:31:57|
|Subject: Where can I learn more about Multi-Version Concurrency Control?|
|Previous:||From: Zeugswetter Andreas SB SD||Date: 2001-08-27 15:25:43|
|Subject: RE: extern + static issue in datetime.c|
pgsql-jdbc by date
|Next:||From: David Daney||Date: 2001-08-27 17:18:42|
|Subject: Re: [JDBC] Re: Bug #428: Another security issue with the JDBC driver.|
|Previous:||From: T.R.Missner||Date: 2001-08-27 15:50:58|
|Subject: Fastpath error on solaris 2.8 pgsql 7.1.3|