In the C-JDBC JDBC Connection driver it uses autoCommit=false to determine if it is in a transaction when changing readOnly.

Unfortunatly LocalManagedConnection sets autoCommit=false prior to "checkState()" which synchronizes the readOnly property with the underlying connection. This approach works fine with most JDBC drivers with but not with C-JDBC. Looking at the JDBC 3 spec (10.1) JDBC says:

"Typically, a new transaction is started when the current SQL statement requires one and there is
no transaction already in place."

The key word being "Typically". So it appears that it may be within C-JDBC's right to declare a transaction started once setAutoCommit=false.

So, would there be any problem with changing LocalManagedConnection.begin() to call checkState() prior to setting autoCommit in the underlying connection?

Mike