Hi, I am wondering whether H2 table locking (not MVCC, but the regular variant) is fair in the sense that, if one transaction locks a table for a while, are other transactions/sessions queued in the order they are trying to attempt to lock the table themselves?
So that, when the first transaction commits, the next transaction that attempted to lock that same table receives the right to do so? Or is the order in which waiting transactions receive the right to lock completely random? Thank you, -hendrik -- 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.
