Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3.13
-
None
Description
When client using CLIENT_FOUND_ROWS, spider returns incorrect matched_rows values (affected_rows)
mysql> update t1 set name='cc' where id=33;
Query OK, 0 rows affected (2.54 sec)
before: Rows matched: 0 Changed: 0 Warnings: 0
now: Rows matched: 1 Changed: 0 Warnings: 0