Details
-
Bug
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.5, 10.6, 10.11, 11.1(EOL), 11.2, 11.4, 10.4(EOL), 11.0(EOL), 11.3(EOL), 11.5(EOL)
Description
# First 3 succeed, last one fails with 'ERROR 1071 (42000): Specified key was too long; max key length is 2000 bytes'
|
CREATE TABLE t1(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=InnoDB;
|
CREATE TABLE t2(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=MyISAM;
|
CREATE TABLE t3(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=MEMORY;
|
CREATE TABLE t4(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=Aria;
|
Leads to:
10.5.6 1c587481966abc7a9ad5309d0a91ca920f7a5657 (Optimized) |
10.5.6>CREATE TABLE t1(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=InnoDB;
|
Query OK, 0 rows affected (0.013 sec)
|
10.5.6>CREATE TABLE t2(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=MyISAM;
|
Query OK, 0 rows affected (0.002 sec)
|
10.5.6>CREATE TABLE t3(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=MEMORY;
|
Query OK, 0 rows affected (0.002 sec)
|
10.5.6>CREATE TABLE t4(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=Aria;
|
ERROR 1071 (42000): Specified key was too long; max key length is 2000 bytes
|
10.4.15 eae968f62d285de97ed607c87bc131cd863d5d03 (Optimized) |
10.4.15>CREATE TABLE t4(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=Aria;
|
ERROR 1071 (42000): Specified key was too long; max key length is 1000 bytes
|
Also note the 1000 vs 2000 inconsistency between 10.4 and 10.5
It is a regression:
10.3.25 bafc5c1321a7dff5f2da292111bf98fed9d1658d (Optimized) |
10.3.25>CREATE TABLE t4(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=Aria;
|
Query OK, 0 rows affected (0.012 sec)
|
10.2.34 (Optimized) |
10.2.34>CREATE TABLE t4(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=Aria;
|
Query OK, 0 rows affected (0.01 sec)
|
10.1.47 (Optimized) |
10.1.47>CREATE TABLE t4(c CHAR(1), UNIQUE KEY i(c) USING HASH) ENGINE=Aria;
|
Query OK, 0 rows affected (0.01 sec)
|
Attachments
Issue Links
- relates to
-
MDEV-17662 Default to UTF8
- Closed
-
MDEV-18791 Wrong error upon creating Aria table with long index on BLOB
- Closed
-
MDEV-21624 Unique index length is able to exceed max key length
- Closed
-
MDEV-22184 UNIQUE key with USING HASH clause changes logic for partitioned tables
- Open
-
MDEV-23713 Replication stops with "Index for table is corrupt", table with HASH index, assertion: !cursor->index->is_committed() fails in row_ins_sec_index_entry_by_modify
- Closed