Re: Consistent Nonlocking Read with REPEATABLE READ and READ COMMTTED
Date: October 19, 2009 11:30PM
I have seen posts stating the same problem that you reported, but for some reason, I am not able to re-produce them. Do you think it has something to do with MySql query browser? I am basically using Query Browser for this; MySql version is 5.1
Session1: create table, start transaction, insert, (do not do anything further)
Session2: select from the same table, "no rows" are returned; which is fair
Session2: commit (this is to advance "time-point"), select from same table, committed data is selected.
Am I doing something diffrent than what you've described? Transaction isolation level is "Repeatable Read" and table is an innodb table.
Originally, I am trying to re-produce why a long running Select on an innodb table locks it? Even in dev, I've seen small selects in Query Browser locks a table for insert/update? Any pointers will be highly appreciated.
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.