Hi > Well, why do you want autocommit to be disabled by default? That you > can disable autocommit in the database URL is more an 'accidental > feature', I don't see it as something that needs to be supported for > all cases. I don't think other databases support disabling autocommit > in the connection URL (do you know any?), so your application would > not be portable. Instead, I suggest to call conn.setAutoCommit(false). >
In almost any application that use a db in transaction mode need to work all the way with autocommit off. Autocommit-on is recommended to avoid by almost any framework, ORM and database vendor. If you can't control the default autocommit mode at connection pool config , you need to plague the code with setAutoCommit(false) in every place where you get a connection.needlessly. > I think that any connection pool (not just the built-in pool of H2) > must reset autocommit at that point. Not doing so would be a bug in > the connection pool implementation (violation of the spec). I don't > see a way to implement your request, sorry. Or do you (or anybody > else) know a way There are some advantage or trade-off using autocommit mode on in H2 ? since it's unrecommended by many reason on others dbms. regards Dario -- You received this message because you are subscribed to the Google Groups "H2 Database" group. 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.
