> > I always commit/rollback transactions, but adding autoCommit=true > > before the connection close did the trick. All of the tests now pass > > without any locking problems. > > I'm sure now it's a bug in the connection pool class, I will fix it in > the next release.
Cool, thanks. > > I have a utility Jdbc.closeSafely(conn) method that I could add > > autoCommit=true to. Of course, adding it to the pool makes sense; but > > it got me thinking--if you detected an autoCommit=false/open > > transaction situation, would you auto-commit for the user or > > auto-rollback? > I think I will implement rollback. Connection.close (when not using > the pool) already rolls back. See the H2 javadocs: > http://www.h2database.com/javadoc/org/h2/jdbc/JdbcConnection.html#close() Makes sense. > (how do you like the new javadoc style by the way?) It looks spiffy--much less cluttered than default javadoc output. - Stephen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to h2-database@googlegroups.com To unsubscribe from this group, send email to h2-database+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/h2-database?hl=en -~----------~----~----~----~------~----~------~--~---
