Hi, On 23 июн, 13:08, hendrik <[email protected]> wrote: > On Jun 23, 9:56 am, hendrik <[email protected]> wrote: > > > Say, I start a transaction on a table, then select and update some > > stuff on it. For that it will be locked. > > Now my guess is, H2 will only unlock the table once I commit or > > rollback the transaction. > > > Correct? > > Did some more reading.. seems like my assumption is correct, if any > updates/inserts occur during the transaction, but not, if only selects > happen. > Please correct me, if I'm wrong.
If you are not using MVCC that's true. > > I assume that once I commit, another waiting connection will be able > > to obtain the lock. > > Will it be *any* waiting connection or will it be the connection that > > has been waiting longest (FIFO)? > > This one I'm still wondering about... Internally it uses java Object.wait() .notifyAll() calls so there are no order guaranties. regards, S.Vladykin -- 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.
