On Sat, Sep 26, 2009 at 9:11 PM, Sergiu Dumitriu <[email protected]> wrote:
This is the first time I hear about it. Looking a bit on its site, I think that this is a good candidate for replacing hsql as the default database (Derby is the other one). There is only one problem I can see with it: choosing the right hibernate dialect. On the H2 documentation, they warn that the official H2Dialect is buggy (how?), but that the hsql dialect can be used.
Ok. There are a few open issues still on Hibernate's side, but I think the warning is kind of old. Though on H2's site they say it works with hsql dialect as well, I wouldn't use it - that gives more problems than solves. I've been using H2Dialect intensively and it has worked in my application that contains some fairly complex queries without any problems. They claim H2 performs much better than either hsql or Derby in most situations and I can assert the claim - I had verified it with my db tests (mostly related to write and transaction performance) running against all three databases, and my results were similar to what they mention at http://www.h2database.com/html/performance.html. Kalle