I don't doubt Brish's technical knowledge, but you should look at his other posts and take what he says with a grain of salt. While everything he is saying may theoretically be true, we have not run into one of the problems he is describing.
We have been using H2 in production for more than a year with databases up to a couple of gig and individual tables up to ~500,000 rows. We use H2 in a single user desktop application. We have run through many, probably hundreds of projects, and we have never lost data to any problems with H2. On a daily basis we have a couple of dozen users connected to H2 databases all day. This includes situations with large transaction and large queries. Generally the query planner does fine and the performance of H2 has been great. You can occasionally run into situations where a particular query will take longer than we expected, but we have always been able to look at the output from the explain command to figure out what was happening. It has always been possible to get the issues straightened out; either through our own efforts or by posting a question to this message board. We have either worked with or evaluated several java databases, and in my opinion none of them are as good as H2. Basically, don't let one person's bias against H2 dissuade you from using it. :-) It is a great database and we have been _very_ happy with it. On Sep 16, 8:24 pm, Brish <[EMAIL PROTECTED]> wrote: > The current issues that I'm aware of are: > > Memory leaks can cause data loss. > > H2 isn't durable. While in most cases you won't lose your data now (a > year ago there were a lot of corruption problems) this can be an issue > for mission critical data. > > H2 has performance problems with large databases because of poor index > use. > > H2 has problems with large transactions (can use memory issues causing > data to be lost). > > H2 has problems with large queries (if the number of results is below > a threshold all data is kept in ram which can cause memory issues > which can result in data loss, if the number of results is above a > threshold it writes it to disk which is really slow). > > In H2 an insert/update/delete locks the table so no other connections > can access the table until the table lock is freed via commit, or > rollback. I think this issue makes h2 unsuitable for a server. > > H2 has one big synchronized lock on the database so you can only run > one query at a time. There is a multithreaded mode but it's unstable > currently. > > Brish > > On Sep 12, 10:57 am, Gili <[EMAIL PROTECTED]> wrote: > > > I was wondering whether the FAQ answer for reliability is up-to-date. > > That is, it sounds like there are still quite a lot of issues that > > remain to be resolved before H2 can be used reliably in production. Is > > this the case? > > > Do you have a rough idea of how long it'll be before it's ready for > > prime time? Are we talking years? > > > Thank you, > > Gili --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
