MySQL Forums
Forum List  »  MaxDB

Share locks in uncommitted isolation level
Posted by: htanguy
Date: March 15, 2007 11:47AM

Hi,

I have the follow strange situation :

isolation level : uncommitted
autocommit off

Transaction 1 modifies a table row R1:
Executes an "Update" request on R1 => produces an exclusive lock on R1.

Transaction 1 not ended.

Transaction 2 begins and reads the same table :
Executes a "Select" request on this table => sometimes this causes shared lock on R1.

Why a shared lock is put on the read row in uncomitted transaction level? Why is it not always repeatable ?

Thank you

Options: ReplyQuote


Subject
Written By
Posted
Share locks in uncommitted isolation level
March 15, 2007 11:47AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.