Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: XAResource implementation
- From: Kris Jurka <books(at)ejurka(dot)com>
- To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
- Cc: joël Winteregg <joel(dot)winteregg(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org, Ludovic Orban <ludovic(dot)orban(at)gmail(dot)com>
- Subject: Re: XAResource implementation
- Date: Wed, 14 Nov 2007 17:11:23 -0500 (EST)
On Tue, 13 Nov 2007, Heikki Linnakangas wrote:
Oh, I had forgotten about that. The difference is the close() between the getConnection()s.I started having second doubts about that case you posted in June, so I tested what Derby does if you call getConnection() twice, without a close in between. You get an error ("Cannot close a connection while a global transaction is still active."), so at least they consider it incorrect as well.
I'm not super happy that explicit close vs implicit close has different transactional behavior, but people really shouldn't be writing code like this, so I've applied your patch to 8.1, 8.2 and HEAD.
Kris Jurka
- Follow-Ups:
- Re: XAResource implementation
- From: joël Winteregg
- Re: XAResource implementation
- References:
- Re: XAResource implementation
- From: joël Winteregg
- Re: XAResource implementation
- From: Heikki Linnakangas
- Re: XAResource implementation
- From: joël Winteregg
- Re: XAResource implementation
- From: Heikki Linnakangas
- Re: XAResource implementation
- From: Kris Jurka
- Re: XAResource implementation
- From: Heikki Linnakangas
- Re: XAResource implementation
- Prev by Date: Re: XAResource implementation
- Next by Date: Re: XAResource implementation
- Previous by thread: Re: XAResource implementation
- Next by thread: Re: XAResource implementation
- Indexes: