revision-id: 77d8f9447661f6147143b21ef43a1ac0f45139b5 (fb-prod201801-199-g77d8f944766) parent(s): 2468ed66a9482fcf2e7b30d53e6eb8561f3c3816 author: Sergei Petrunia committer: Sergei Petrunia timestamp: 2019-01-28 00:35:40 +0300 message: Update test result With Range Locking, DML queries behave like Read-Committed, even if @@tx_isolation=Repeatable-Read (Just like with InnoDB) --- mysql-test/suite/rocksdb/r/level_repeatable_read-range_locking.result | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/mysql-test/suite/rocksdb/r/level_repeatable_read-range_locking.result b/mysql-test/suite/rocksdb/r/level_repeatable_read-range_locking.result index 3c5f1c2bf7c..37dc45a17f4 100644 --- a/mysql-test/suite/rocksdb/r/level_repeatable_read-range_locking.result +++ b/mysql-test/suite/rocksdb/r/level_repeatable_read-range_locking.result @@ -99,7 +99,7 @@ INSERT INTO t3 (pk) VALUES(1) ON DUPLICATE KEY UPDATE count=count+1; COMMIT; SELECT count FROM t3; count -0 +1 connection default; disconnect con1; disconnect con2;