[Monetdb-developers] SQL/JDBC: autocommit state
Hi All, I have almost filed a bug, but noticed [ 1394298 ] SQL: auto commit state is not changed correctly on commithttps://sourceforge.net/tracker/index.php?func=detail&aid=1394298&group_id=56967&atid=482468 so I decided to discuss the problem here first. My JDBC-based application stopped working with MonetDB 4.10.0/sql 2.10.0, while it works OK with Postgres backend and it used to work with MonetDB 4.9.3/sql 2.9.3. It output "commit does not allowed in autocommit mode" exceptions. However, I am sure that application handles transaction itself, that is setAutoCommit(false) is called immediately after connection is established and the connections are never return to autocommit mode. I investigated and found out that connection is switched to autocommit mode after commit() is called. I think server should not switch to autocommit mode after java.sql.Connection.commit() or java.sql.Connection.rollback(). Though this is not explicitly defined by JDBC specs, as far as I know all JDBC drivers work in this way, so it is standard de-facto. Therefore I suggest to revert the change. -- Best regards, Andrei Martsinchyk mailto:andrei.martsinchyk@gmail.com
On 30-01-2006 21:22:54 +0200, Andrei Martsinchyk wrote:
Hi All,
I have almost filed a bug, but noticed [ 1394298 ] SQL: auto commit state is not changed correctly on commithttps://sourceforge.net/tracker/index.php?func=detail&aid=1394298&group_id=56967&atid=482468
Please file a bug. This is closely related.
I think server should not switch to autocommit mode after java.sql.Connection.commit() or java.sql.Connection.rollback().
I don't think so either, so it is indeed a bug. I'll look into this, but please also report a bug so we can track it. Regards, Fabian
participants (2)
-
Andrei Martsinchyk
-
Fabian Groffen