Hi, Did you already read the documentation at http://h2database.com/html/advanced.html#transaction_isolation ? The documentation is not complete, I will add:
= Read Committed = Read locks are released immediately after executing the statement, but write locks are kept until the transaction commits. = Serializable = Both read locks and write locks are kept until the transaction commits. > Will it be *any* waiting connection or will it be the connection that > has been waiting longest (FIFO)? One of the waiting connections is picked at random (not FIFO). I will also document that. I tried FIFO (java.util.concurrent.locks.ReentrantLock(true)) and it's a *lot* slower (100 times?), that's why I don't plan to use it. > state of mvcc? Still beta and/or unstable? I would still call it "beta", but there are no known problems since quite a long time. Regards, Thomas -- 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.
