Re: table locking expected behavior

[KimSeong Loh]

Write locks takes priority over read locks unless you specify otherwise, thats all. It should not matter whether it is an explicit or implicit locks. That is as far as I understand it.

So, it is important to know if the locks in #2 and #3 are read or write.

Assuming the oder is that #2 read is received before #3 locks when #1 has write locked the table.

When #1 finishes and release the lock,
if #3 is a write lock, the #3 will get the lock first and #2 (read) will have to wait.
if #3 is a read lock, the it queues behid #2 which is also a read lock, both can continue if there is no connection waiting for a write lock on the table, since a read lock can be shared.






Edited 1 time(s). Last edit at 01/20/2006 11:28PM by KimSeong Loh.