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 -~----------~----~----~----~------~----~------~--~---
