Re: Serializable transactions and SQLException

On Thu, 28 Oct 2004, Giampaolo Tomassoni wrote:

> I would like to develop java code using the pgsql-jdbc driver on
> serializable isolated transactions. The (general) pgsql manual states
> that this, of course, may cause concurrent updating transaction failures
> to inform the client to retry the transaction as a whole.
>
> This is said to be reported by the error message:
>
> ERROR: Can't serialize access due to concurrent update
>
>
> Great. I want to cope with it. But what's the SQLException.getSQLState() value
> associated to this? Or is it a SQLException.getErrorCode()? Is this value
> something 'standard', in the sense that, ie., if I need to switch to Oracle
> it works fine? Is there a better way to identify 'please, retry' suggestions
> than browsing the SQLException object?

If you are connected to a >= 7.4 server getSQLState will have a value for
this error. The best way to identify it and make sure you code works on
other database platforms is to actually write a small test case to
generate this error and grab the error code. PG will always return
the same error code, but other databases may not use the same one and the
best way to find out is actually testing.

Kris Jurka