Details
-
Bug
-
Status: Confirmed (View Workflow)
-
Major
-
Resolution: Unresolved
-
10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL), 10.11, 11.0(EOL), 11.1(EOL)
Description
Present in InnoDB, MyISAM, Aria but not in MEMORY.
CREATE TABLE t (b INT AUTO_INCREMENT KEY); |
CREATE UNIQUE INDEX i USING HASH ON t(b); |
or
CREATE TABLE t (b INT AUTO_INCREMENT KEY); |
ALTER TABLE t ADD UNIQUE id USING HASH (b); |
Leads to:
10.10.0 e1caa4bd5e8b4645944b85d4b603bf9fc9ef6ca4 (Optimized) |
10.10.0-opt>ALTER TABLE t ADD UNIQUE id USING HASH (b);
|
ERROR 1901 (HY000): Function or expression 'AUTO_INCREMENT' cannot be used in the USING HASH clause of `b`
|
10.10.0 e1caa4bd5e8b4645944b85d4b603bf9fc9ef6ca4 (Optimized) |
2022-07-29 18:36:43 4 [ERROR] mysqld: Incorrect information in file: './test/#sql-alter-d1832-4.frm'
|
Bug confirmed present in:
MariaDB: 10.4.26 (dbg), 10.4.26 (opt), 10.5.17 (dbg), 10.5.17 (opt), 10.6.9 (dbg), 10.6.9 (opt), 10.7.5 (dbg), 10.7.5 (opt), 10.8.4 (dbg), 10.8.4 (opt), 10.9.2 (dbg), 10.9.2 (opt), 10.10.0 (dbg), 10.10.0 (opt)
Bug (or feature/syntax) confirmed not present in:
MariaDB: 10.3.36 (dbg), 10.3.36 (opt)
MySQL: 5.5.62 (dbg), 5.5.62 (opt), 5.6.51 (dbg), 5.6.51 (opt), 5.7.38 (dbg), 5.7.38 (opt), 8.0.29 (dbg), 8.0.29 (opt)
Attachments
Issue Links
- is caused by
-
MDEV-371 Unique indexes for blobs
- Closed
- is duplicated by
-
MDEV-28192 ERROR 1901 During ALTER Leading to frm table corruption
- Closed
-
MDEV-28238 Incorrect information in file: './test/#sql-alter-......frm' on ALTER TABLE ... ADD UNIQUE ... USING HASH
- Closed