[MDEV-27329] Wrong result upon LIKE with geostd8_nopad collations and index Created: 2021-12-20  Updated: 2023-03-03

Status: Open
Project: MariaDB Server
Component/s: Character Sets, Optimizer
Affects Version/s: 10.5, 10.6, 10.7
Fix Version/s: 10.5, 10.6

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Alexander Barkov
Resolution: Unresolved Votes: 0
Labels: None


 Description   

CREATE TABLE t (c char(32), KEY (c)) ENGINE=MyISAM collate geostd8_nopad_bin;
INSERT INTO t VALUES ('r'),('rock'),('rr');
SELECT c FROM t WHERE c LIKE 'r%';
 
# Cleanup
DROP TABLE t;

10.5 2776635c

SELECT c FROM t WHERE c LIKE 'r%';
c
rock
rr

Same with geostd8_general_nopad_ci collation, but not, for example, with geostd8_general_ci.

Since it only happens with a key, I don't suppose it's a feature of these collations.

Reproducible on 10.5+ with MyISAM and Aria.
Not reproducible on 10.4.
Not reproducible with InnoDB.



 Comments   
Comment by Alice Sherepa [ 2022-12-02 ]

probably the same as MDEV-27632

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