Michael Allman wrote:
> On Wed, 27 Jul 2005, Oliver Jowett wrote:
>> More generally: can we get XAExceptions thrown with useful messages? It
>> seems like there's no direct constructor that gives you both message and
>> error code, but the error code is a public field so you can set it after
>> construction before throwing.
> Since the client of a PGXAResource instance is a transaction manager I
> see no benefit. The transaction manager will make a decision on what to
> do based on the code carried by XAException and carry on. Maybe it will
> log a message.
I absolutely disagree with there being no benefit. We should provide as
much information as possible in the exception. All hhe TM *has* to log
is the exception we give it, really, so that better have all the
information we can give about any underlying problems.
In response to
pgsql-jdbc by date
|Next:||From: Les Carter||Date: 2005-07-27 05:00:25|
|Subject: unusual ResultSet.next() behaviour|
|Previous:||From: Oliver Jowett||Date: 2005-07-27 04:33:18|
|Subject: Re: jdbc xa patches|