Commit 24d27e3b authored by kostja@dipika.(none)'s avatar kostja@dipika.(none)

Update Bug#12713 test results to take into account fixed bugs (29157, 33846)

parent 566ca2ba
...@@ -421,15 +421,10 @@ call p_verify_status_increment(2, 2, 2, 2); ...@@ -421,15 +421,10 @@ call p_verify_status_increment(2, 2, 2, 2);
--echo # 4. Read-write statement: UPDATE, update 0 rows, 1 row matches WHERE --echo # 4. Read-write statement: UPDATE, update 0 rows, 1 row matches WHERE
--echo # --echo #
--echo # Note the wrong Handler_prepare/Handler_commit count is due to
--echo # Bug#29157 "UPDATE, changed rows incorrect" and
--echo # Bug#Bug #33846 UPDATE word:Wrong 'Changed rows' if InnoDB, unique
--echo # key and no rows qualify WHERE
--echo #
update t1 set a=2; update t1 set a=2;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
commit; commit;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
--echo # 5. Read-write statement: UPDATE, update 0 rows, 0 rows match WHERE --echo # 5. Read-write statement: UPDATE, update 0 rows, 0 rows match WHERE
--echo # --echo #
...@@ -483,9 +478,9 @@ call p_verify_status_increment(2, 2, 2, 2); ...@@ -483,9 +478,9 @@ call p_verify_status_increment(2, 2, 2, 2);
--echo # 10. Read-write statement: REPLACE, change 0 rows. --echo # 10. Read-write statement: REPLACE, change 0 rows.
--echo # --echo #
replace t1 set a=1; replace t1 set a=1;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
commit; commit;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
--echo # 11. Read-write statement: IODKU, change 1 row. --echo # 11. Read-write statement: IODKU, change 1 row.
--echo # --echo #
......
...@@ -416,17 +416,12 @@ SUCCESS ...@@ -416,17 +416,12 @@ SUCCESS
# 4. Read-write statement: UPDATE, update 0 rows, 1 row matches WHERE # 4. Read-write statement: UPDATE, update 0 rows, 1 row matches WHERE
# #
# Note the wrong Handler_prepare/Handler_commit count is due to
# Bug#29157 "UPDATE, changed rows incorrect" and
# Bug#Bug #33846 UPDATE word:Wrong 'Changed rows' if InnoDB, unique
# key and no rows qualify WHERE
#
update t1 set a=2; update t1 set a=2;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
SUCCESS SUCCESS
commit; commit;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
SUCCESS SUCCESS
# 5. Read-write statement: UPDATE, update 0 rows, 0 rows match WHERE # 5. Read-write statement: UPDATE, update 0 rows, 0 rows match WHERE
...@@ -496,11 +491,11 @@ SUCCESS ...@@ -496,11 +491,11 @@ SUCCESS
# 10. Read-write statement: REPLACE, change 0 rows. # 10. Read-write statement: REPLACE, change 0 rows.
# #
replace t1 set a=1; replace t1 set a=1;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
SUCCESS SUCCESS
commit; commit;
call p_verify_status_increment(2, 2, 2, 2); call p_verify_status_increment(2, 2, 1, 0);
SUCCESS SUCCESS
# 11. Read-write statement: IODKU, change 1 row. # 11. Read-write statement: IODKU, change 1 row.
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment