Don't get me wrong, but relying upon a clearly documented feature (in bold!) is certainly not doggy behavior =)
setAutoCommit is certainly not meant to be just called once (just think of connections that are being reused by different pieces of code with different autocommit demands). After all, that is why the method is there: so that the autocommit behavior is not fixed for the lifetime of the connection. To be more precise, just in case somebody plans to fix this: please be aware that a solid JDBC driver should be able to cope with any sequence of .commit/.rollback/.setAutoCommit/.setReadOnly calls (and maybe setTransactionIsolation, but then the exact outcome is open to the JDBC implementation, see the javadocs for setTransactionIsolation). Thanks for eventually having a look at this! -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/JikGBiLDsFsJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
