Skip site navigation (1) Skip section navigation (2)

Re: jdbc xa patches

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Michael Allman <msa(at)allman(dot)ms>
Cc: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: jdbc xa patches
Date: 2005-07-27 04:35:10
Message-ID: 42E70EFE.20600@opencloud.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
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.

-O

In response to

Responses

pgsql-jdbc by date

Next:From: Les CarterDate: 2005-07-27 05:00:25
Subject: unusual ResultSet.next() behaviour
Previous:From: Oliver JowettDate: 2005-07-27 04:33:18
Subject: Re: jdbc xa patches

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group