One minor correction in my original post - we use H2 DB in embedded mode, and not in-memory.
However, this should not change the overall magnitude of the query. On Thursday, 23 May 2013 17:15:57 UTC+5:30, aditya wrote: > > Hi, > > I wanted to know if it is recommended to use the MVCC parameter with an > in-memory h2 database and > are there any risks involved if it is used in production environment? > We have some scenarios wherein concurrent access to DB is required and if > MVCC is not used, > it results in error 'timeout trying to lock table' (even on SELECT queries > and in cases where we have nested transactions). > We are using H2 version 1.2.147 but if required we can switch to the latest > version. > However, even the latest H2 documentation says that MVCC feature is still > experimental. > And are there any other alternatives to MVCC, to achieve better concurrency > in such situations? A quick response would be highly appreciated. > > Thanks, > > Aditya > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
