Skip to:
I observed the following case, which looks like a bug for isolation level "repeatable read" from my point of view I have table:
connect to mysql server as slave by using libslave
update the record
received this update through libslave.
create a new connection and make query "SELECT status FROM campaign WHERE id=1"
expected that status will be "active", but actually status is "deleted"
if I change the isolation level to "Read-Commited", I get the status "active" in step 5 as expected.
Adding read lock in previous query also works. the query
also returns status "active" even isolation level is "repeatable read"
Closed as "Cannot Reproduce", because we cannot repeat the issue on our side and the reporter did not provide additional informaiton.
Thank you for the report. I cannot repeat described behavior using command line client:
Session 1:
Session 2:
How do you create connection at step 4?
I observed the following case, which looks like a bug for isolation level "repeatable read" from my point of view
I have table:
connect to mysql server as slave by using libslave
update the record
received this update through libslave.
create a new connection and make query "SELECT status FROM campaign WHERE id=1"
expected that status will be "active", but actually status is "deleted"
if I change the isolation level to "Read-Commited", I get the status "active" in step 5 as expected.
Adding read lock in previous query also works. the query
also returns status "active" even isolation level is "repeatable read"