Actually, for primarily read situations, I've found H2 to be fine for concurrent use with the default configuration. The table-level locking only really becomes an issue when you have mixed updates and queries.
Be sure to give it lots of cache though. Chris On Mon, Jul 20, 2009 at 12:49 PM, DinamicaFramework < [email protected]> wrote: > > Hi, I arrived today to this list, already searched past mesages over > this subject, but could not found any recent messages about it. I > understand that H2 primary focus is on the embedded DB market, but I > wonder if there has been improvements in the past months to make it > usable as a standalone server that can run concurrent queries from > remote clients without blocking? I am thinking mainly about using it > as a database server for webapps with a light load, but supporting a > mixed load of short and long running queries without blocking each > other, is this possible with the current version? > > Regards, > Martin Cordova > http://www.martincordova.com > > > > -- C. Schanck --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
