Hi, We added db_close_delay because we have tests that open a Hibernate Session > (connection), do some work, close that Session (thus closing that > connection), open a new Session and try to do some work with the stuff done > in the initial Session. But H2 had dropped the database in between. >
Yes, I understand that. That's fine. But if you want to enable MVCC in one case, and disable it in another case, then you need to use two different databases. The easiest way is to use different database names. That's why I wrote: jdbc:h2:mem:db1;DB_CLOSE_DELAY=-1;MVCC=TRUE jdbc:h2:mem:db2;DB_CLOSE_DELAY=-1;MVCC=FALSE Please note "db1" in one case, and "db2" in the other case. There are other options, but that's probably the easiest one. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
