Hi,
On the main page, in the feature comparison, it show that HSQLDB does
not support MVCC, while HSQLDB 2.0.0 does in fact support MVCC.
Also HSQLDB does support transaction isolation, at least READ COMMITTED
and SERIALIZABLE. See: http://hsqldb.org/web/features200.html
Also, in the interests of fairness, maybe an entry indicating that
HSQLDB supports multi-threaded MVCC, while H2 does not. A feature
comparison where one side has all blocks checked, and everything else is
lacking immediately makes me think, "So, what are that not telling me?".
Think about it using the iceberg principle. H2, when comparing itself
with other DBs fails to mention x, y and z, which would even the scales
considerably. So, this is the top of the iceberg that I can see clearly
be looking at the HSQLDB website, what else is lurking beneath the surface?
I think an honest comparison would INCREASE my confidence in H2. Maybe
the feature comparison is out of date, after all, HSQLDB 2.0.0 was only
released this month...
Thanks,
Jesse
--
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.
