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?

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
    (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Reply via email to