Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.5, 10.6, 5.5(EOL), 10.0(EOL), 10.1(EOL), 10.3(EOL), 10.4(EOL), 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
Description
This bug is known for a long time since adding UCA collations.
This script with no index:
DROP TABLE IF EXISTS t1;
|
CREATE TABLE t1 (a VARCHAR(10) CHARACTER SET utf8 COLLATE utf8_unicode_ci);
|
INSERT INTO t1 VALUES ('a'),('b'),('c'),('d'),('e'),('f'),('g'),('h');
|
SELECT * FROM t1 WHERE a<'\0b';
|
and this script with KEY(a):
DROP TABLE IF EXISTS t1;
|
CREATE TABLE t1 (a VARCHAR(10) CHARACTER SET utf8 COLLATE utf8_unicode_ci, KEY(a));
|
INSERT INTO t1 VALUES ('a'),('b'),('c'),('d'),('e'),('f'),('g'),('h');
|
SELECT * FROM t1 WHERE a<'\0b';
|
correctly return one row:
+------+
|
| a |
|
+------+
|
| a |
|
+------+
|
1 row in set (0.00 sec)
|
This script with a prefix index KEY(a(1))
DROP TABLE IF EXISTS t1;
|
CREATE TABLE t1 (a VARCHAR(10) CHARACTER SET utf8 COLLATE utf8_unicode_ci, KEY(a(1)));
|
INSERT INTO t1 VALUES ('a'),('b'),('c'),('d'),('e'),('f'),('g'),('h');
|
SELECT * FROM t1 WHERE a<'\0b';
|
erroneously returns empty set.
Attachments
Issue Links
- relates to
-
MDEV-8626 Bad result set with expansions when using a prefix key
- Confirmed
-
MDEV-20884 Different resultset when using prefix index and utf8mb4
- Confirmed
-
MDEV-34611 INNER JOIN returns incorrect results
- Stalled