On Wed, 12 Jan 2005, Oliver Jowett wrote:
> Looking at the code, it looks like fireConnectionFatalError() isn't
> being called in the normal execution (non-setup) path at all.
Yes, this is the root of the problem.
> I will look at fixing this. Probably the best way to do it is monitor
> the SQLState of thrown exceptions in the InvocationHandler and know
> about which states are fatal (e.g. connection failure, driver internal
> errors).
>
That could work, although coming up with the list of fatal states might be
tricky. I've never paid much attention to the sql states that the driver
assigns itself, this might be the time to change that and remove the
PSQLException constructor that doesn't take a PSQLState argument.
Kris Jurka