[MDEV-15973] System versioning and MROONGA don't work well together: WARN_DATA_TRUNCATED makes DELETEs be ignored Created: 2018-04-22  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - Mroonga, Versioned Tables
Affects Version/s: 10.3
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: None


 Description   

INSTALL SONAME 'ha_mroonga';
 
CREATE OR REPLACE TABLE t1 (i INT PRIMARY KEY) ENGINE=Mroonga WITH SYSTEM VERSIONING;
INSERT INTO t1 VALUES (1);
DELETE FROM t1;
SELECT * FROM t1;
SELECT i, row_start, row_end FROM t1 FOR SYSTEM_TIME ALL;
 
# Cleanup
DROP TABLE t1;
UNINSTALL SONAME 'ha_mroonga';

10.3 c39f8a80c9fe

DELETE FROM t1;
Warnings:
Warning	1265	data truncated for primary key column: <row_end>
SELECT * FROM t1;
i
1
SELECT i, row_start, row_end FROM t1 FOR SYSTEM_TIME ALL;
i	row_start	row_end
1	2018-04-22 13:58:34.397398	2038-01-19 05:14:07.999999

So far I haven't heard from any MariaDB users who would actually use Mroonga (only those who had troubles with it while building the server), so I doubt that fixing it in 10.3 worth the trouble, maybe again, just disable versioning for Mroonga (if such disabling is possible at all).


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