[MCOL-2239] Rows matched: and Changed: are 0 even if rows changed after update Created: 2019-03-14  Updated: 2021-10-01  Resolved: 2020-01-30

Status: Closed
Project: MariaDB ColumnStore
Component/s: MDB Plugin
Affects Version/s: 1.2
Fix Version/s: 1.4.3

Type: Bug Priority: Major
Reporter: Richard Stracke Assignee: Roman
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Relates
relates to MCOL-4536 update returns wrong number of rows u... Closed
relates to MCOL-1527 Incorrect 0 row(s) affected on delete... Closed
relates to MCOL-1782 UPDATE and DELETE reported incorrect ... Closed

 Description   

To reproduce:

 create table t1 (c1 int) engine=columnstore;
 
insert into t1 (c1) values(1);
 
insert into t1 (c1) values(2);
 
update t1 set c1 = c1 +1;

Rows matched and Changed --> 0

Query OK, 2 rows affected (0.516 sec)
 
Rows matched: 0  Changed: 0  Warnings: 0

The same testcase works with InnoDB

 create table t1inno (c1 int) engine=columnstore;
 
insert into t1inno (c1) values(1);
 
insert into t1inno (c1) values(2);
 
update t1inno set c1 = c1 +1;


Query OK, 2 rows affected (0.056 sec)
 
Rows matched: 2  Changed: 2  Warnings: 0



 Comments   
Comment by David Hall (Inactive) [ 2020-01-30 ]

This works after all the new handlers were implemented in 1.4.3. Fixing in 1.2.6 is a resource cost we choose to not undertake.

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