[MDEV-21694] CHECK under EMPTY_STRING_IS_NULL reports a misplaced row on partitioned table with virtual column Created: 2020-02-09  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Partitioning, Virtual Columns
Affects Version/s: 10.3, 10.4
Fix Version/s: 10.4

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Nikita Malyavin
Resolution: Unresolved Votes: 0
Labels: None


 Description   

--source include/have_partition.inc
 
CREATE TABLE t1 (b BINARY GENERATED ALWAYS AS ('') VIRTUAL) PARTITION BY KEY(b) PARTITIONS 2;
INSERT INTO t1 () VALUES ();
FLUSH TABLES;
SET SQL_MODE= CONCAT(@@sql_mode,',EMPTY_STRING_IS_NULL');
CHECK TABLE t1;
 
# Cleanup
DROP TABLE t1;

10.3 d72038a7

CHECK TABLE t1;
Table	Op	Msg_type	Msg_text
test.t1	check	error	Found a misplaced row
test.t1	check	error	Partition p1 returned error
test.t1	check	error	Upgrade required. Please do "REPAIR TABLE `t1`" or dump/reload to fix it!

Reproducible with at least MyISAM and InnoDB on 10.3-10.5.
The test case is not applicable to 10.2 due to the sql mode.


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