Closed GoogleCodeExporter closed 9 years ago
While I understand the problem, I'm afraid there is little I can do because the
connection pool implementation (could be a third part) is supposed to enable
autocommit. But I will change the SET AUTOCOMMIT documentation:
-----------
SET AUTOCOMMIT { TRUE | ON | FALSE | OFF }
Switches auto commit on or off. This setting can be appended to the database
URL:
jdbc:h2:test;AUTOCOMMIT=OFF - however this will not work as expected when using
a
connection pool (the connection pool manager will re-enable autocommit when
returning
the connection to the pool, so autocommit will only be disabled the first time the
connection is used).
-----------
Therefore, I'm setting the bug to "Won't Fix"
Original comment by thomas.t...@gmail.com
on 19 Apr 2010 at 5:14
Totally fair. Thanks.
Original comment by joe.witt
on 20 Apr 2010 at 1:31
Original issue reported on code.google.com by
joe.witt
on 15 Apr 2010 at 1:36