Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5, 10.6, 10.7(EOL)
-
None
Description
This bug is similar for MDEV-26743, but for MyISAM.
The same problem is repeatable with:
- ENGINE=Aria
- ENGINE=MEMORY in combination with BTREE index algorithm.
Basic latin letter vs equal accented letter
SET NAMES utf8mb3; |
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a CHAR(2), PRIMARY KEY(a)) COLLATE utf8_unicode_nopad_ci ENGINE=MyISAM; |
INSERT INTO t1 VALUES ('a'),('ä'); |
Query OK, 2 rows affected (0.001 sec)
|
Records: 2 Duplicates: 0 Warnings: 0
|
Looks wrong. The expected result is to throw a duplicate key error. See MDEV-26743 for details.
Two letters vs equal (but space padded) expansion
SET NAMES utf8mb3; |
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a CHAR(2), PRIMARY KEY(a)) COLLATE utf8_unicode_nopad_ci ENGINE=MyISAM; |
INSERT INTO t1 VALUES ('ss'),('ß'); |
ERROR 1062 (23000): Duplicate entry 'ß' for key 'PRIMARY'
|
Looks wrong. The expected result is to accept both values. See MDEV-26743 for details.
Basic latin letter (but followed by an ignorable character) vs equal accented letter
SET NAMES utf8mb3; |
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a CHAR(3), PRIMARY KEY(a)) CHARACTER SET utf8mb3 COLLATE utf8mb3_unicode_nopad_ci ENGINE=MyISAM; |
INSERT INTO t1 VALUES (CONCAT('a',_utf8mb3 0x01)),('ä'); |
ERROR 1062 (23000): Duplicate entry 'ä' for key 'PRIMARY'
|
Looks wrong. The expected result is to accept both values. See MDEV-26743 for details.
SET NAMES utf8mb3; |
DROP TABLE IF EXISTS t1; |
CREATE TABLE t1 (a CHAR(2), PRIMARY KEY(a)) COLLATE utf8_unicode_nopad_ci ENGINE=MyISAM; |
INSERT INTO t1 VALUES (CONCAT('a',_utf8mb3 0x01)),('ä'); |
ERROR 1062 (23000): Duplicate entry 'ä' for key 'PRIMARY'
|
Looks wrong. The expected result is to accept both values. See MDEV-26743 for details.
Attachments
Issue Links
- relates to
-
MDEV-25440 Assertion `cmp_rec_rec(rec, old_rec, offsets, old_offsets, m_index) > 0' failed in PageBulk::insert
- Closed
-
MDEV-25449 Add MY_COLLATION_HANDLER::strnncollsp_nchars()
- Closed
-
MDEV-25904 New collation functions to compare InnoDB style trimmed NO PAD strings
- Closed
-
MDEV-26743 InnoDB: CHAR+nopad does not work well
- Closed