Re: commit and rollback don't throw exceptions when they should - Mailing list pgsql-jdbc

From Kris Jurka
Subject Re: commit and rollback don't throw exceptions when they should
Date
Msg-id alpine.BSO.2.00.0911180619360.13019@leary.csoft.net
Whole thread Raw
In response to Re: commit and rollback don't throw exceptions when they should  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: commit and rollback don't throw exceptions when they should
List pgsql-jdbc

On Wed, 4 Nov 2009, Kevin Grittner wrote:

> Having received no feedback on the preliminary patch I previously
> posted, I'll suggest this (fairly minimal) patch.  I didn't attempt to
> deal with the distributed transaction issue, since it seemed pretty
> messy and I wasn't sure the fix was worth the mess it would make.  As
> far as I can see, it should fix the OP's problem, although it would be
> nice to get a confirmation of that.
>

I've commited a modified version of this patch to HEAD only, because
changing this behavior could break peoples applications.

I extended the check for the connection already being closed to the other
connection methods.  There's no reason commit/rollback are special here.
I also needed to fix a regression testcase which was violating this rule.

Kris Jurka


pgsql-jdbc by date:

Previous
From: Maciek Sakrejda
Date:
Subject: COPY and turning off autocommit
Next
From: Kris Jurka
Date:
Subject: Re: [BUGS] BUG #5177: Concurrency problem in AbstractJdbc23PooledConnection