Yeah: Thanks for this great 1.4.200 H2 release:
We had bugs in our tests, which weren't found because of bugs in H2. Now
these bugs in H2 are fixed :)
Background: It seems that it could happen in 1.4.199, that being in a
schema a select from a table which doesn't exist (being on the wrong
sche
Thank you for your fast reply.
Without the MVCC param, I receive some test failures which I don't get with
H2 1.4.199. I'll dive into this and post my results
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and st
Just drop the MVCC param, it will use MVSTore by default, even for in-mem
databases, which is naturally an MVCC engine
--
You received this message because you are subscribed to the Google Groups "H2
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an emai
Hmm, [1] states that MVStore should support in-memory-usage and MVCC.
Perhaps its only a usage problem with correct connection URL params for my
case?
[1]
http://www.h2database.com/html/mvstore.html?highlight=Mvcc&search=MVCC#inMemory
--
You received this message because you are subscribed t
