From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Daniel Migowski <dmigowski(at)ikoffice(dot)de>, "pgsql-jdbc(at)postgresql(dot)org" <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Bug: Transaction still open after error when autocommit=true |
Date: | 2011-12-23 01:00:07 |
Message-ID: | CADK3HHJ8TpocbPD7=HKP0AKmFV9nFUqB5dwjPCULuC1v+kJucg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Clearly the exception that is thrown when you try to rollback is that
autocommit is on.
I don't really see this as a bug.
Dave Cramer
dave.cramer(at)credativ(dot)ca
http://www.credativ.ca
On Thu, Dec 22, 2011 at 6:29 PM, Kevin Grittner
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Daniel Migowski <dmigowski(at)ikoffice(dot)de> wrote:
>
>> A small demo for the bug is attached.
>
> The javadocs for Connection:
>
> http://docs.oracle.com/javase/6/docs/api/java/sql/Connection.html
>
> say:
>
> | JDBC applications should use the appropritate Connection method
> | such as setAutoCommit or setTransactionIsolation. Applications
> | should not invoke SQL commands directly to change the connection's
> | configuration when there is a JDBC method available.
>
> I take that to mean that the right way to do this is to set
> autoCommit to false and use the connection's commit() method. If
> you do it that way, is there a problem?
>
> -Kevin
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2011-12-23 01:56:49 | Re: Bug: Transaction still open after error when autocommit=true |
Previous Message | Kevin Grittner | 2011-12-22 23:29:18 | Re: Bug: Transaction still open after error when autocommit=true |