Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.4(EOL), 10.5, 10.6, 10.7(EOL), 10.8(EOL), 10.9(EOL), 10.10(EOL)
Description
CREATE TABLE t (a INT AUTO_INCREMENT KEY) ENGINE=InnoDB; |
ALTER TABLE t ADD UNIQUE u USING HASH (a); |
Leads to:
10.9.0 5be92887c2caacb45af87b1131db952ce627e83a (Optimized and Debug) |
10.9.0-opt>ALTER TABLE t ADD UNIQUE u USING HASH (a);
|
ERROR 1901 (HY000): Function or expression 'AUTO_INCREMENT' cannot be used in the USING HASH clause of `a`
|
10.9.0 5be92887c2caacb45af87b1131db952ce627e83a (Debug) |
2022-03-29 18:00:32 4 [ERROR] mysqld: Incorrect information in file: './test/#sql-alter-870e-4.frm'
|
10.9.0 5be92887c2caacb45af87b1131db952ce627e83a (Optimized) |
2022-03-29 18:14:23 4 [ERROR] mysqld: Incorrect information in file: './test/#sql-alter-140c3c-4.frm'
|
Bug confirmed present in:
MariaDB: 10.4.25 (dbg), 10.4.25 (opt), 10.5.16 (dbg), 10.5.16 (opt), 10.6.8 (dbg), 10.6.8 (opt), 10.7.4 (dbg), 10.7.4 (opt), 10.8.3 (dbg), 10.8.3 (opt), 10.9.0 (dbg), 10.9.0 (opt)
Bug (or feature/syntax) confirmed not present in:
MariaDB: 10.2.44 (dbg), 10.2.44 (opt), 10.3.35 (dbg), 10.3.35 (opt)
MySQL: 5.5.62 (dbg), 5.5.62 (opt), 5.6.51 (dbg), 5.6.51 (opt), 5.7.37 (dbg), 5.7.37 (opt), 8.0.28 (dbg), 8.0.28 (opt)
Attachments
Issue Links
- duplicates
-
MDEV-29203 Incorrect information in file: ... #sql-alter ... .frm on ALTER when adding unique hash index, ERROR 1901
- Confirmed
- is caused by
-
MDEV-371 Unique indexes for blobs
- Closed
- relates to
-
MDEV-22759 Failing assertion: !cursor->index->is_committed() upon update on table with HASH index
- Confirmed