Hi All,<br>
<br>
I have almost filed a bug, but noticed <br>
<a href="https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1394298&amp;group_id=56967&amp;atid=482468">[ 1394298 ] SQL: auto commit state is not changed correctly on commit</a><br clear="all">so I decided to discuss the problem here first.
<br>
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 &quot;commit does not allowed in
autocommit mode&quot; exceptions. However, I am sure that application&nbsp;
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.<br>
I think server should not switch to autocommit mode after java.sql.Connection.commit() or java.sql.Connection.rollback().<br>
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.<br>
Therefore I suggest to revert the change.<br>
<br>-- <br>Best regards,<br>Andrei
Martsinchyk&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
mailto:<a href="mailto:andrei.martsinchyk@gmail.com">andrei.martsinchyk@gmail.com</a>