[MDEV-18973] CLIENT_FOUND_ROWS wrong in spider Created: 2019-03-20  Updated: 2019-12-16  Resolved: 2019-12-16

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Spider
Affects Version/s: 10.3.13
Fix Version/s: 10.4.11

Type: Bug Priority: Critical
Reporter: liangfeilong Assignee: Kentoku Shiba (Inactive)
Resolution: Fixed Votes: 0
Labels: 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

 Comments   
Comment by willhan [ 2019-05-11 ]

Hi kentoku
I have push a commit for this issue.
The commit id is 0a3c2d4

Comment by Kentoku Shiba (Inactive) [ 2019-11-11 ]

Meraged, fixed, add tests and pushed.
0cf2ebd

Comment by Kentoku Shiba (Inactive) [ 2019-11-29 ]

pushed to 10.4

Generated at Thu Feb 08 08:48:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.