On Mon, 24 May 2004, Oliver Jowett wrote:
> The implementation of SQLState (or connectionErrorOccurred) across
> different drivers is quite patchy. When writing portable applications
> (or even driver-specific applications, to a lesser extent) you have to
> assume that any SQLException you don't specifically recognize means your
> connection is toast.
>
I think a reasonable coding method would be to catch an SQLException try
to rollback and if that throws an Exception then you give up the
Connection.
Kris Jurka