Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.4(EOL)
-
None
Description
Note: The failure became possible after MDEV-371, without it ALTER is rejected due to the missing length in the key definition.
See also MDEV-18708 and MDEV-18709, might be related or have the same root cause. MDEV-18709 has a very similar test case.
--source include/have_innodb.inc
|
|
CREATE TABLE t1 ( |
pk INT, |
a CHAR(100), |
b INT, |
c CHAR(100), |
PRIMARY KEY(pk), |
KEY(a(64)), |
KEY(pk,b), |
KEY(c(64)) |
) ENGINE=InnoDB;
|
ALTER TABLE t1 MODIFY b TEXT; |
|
# Cleanup
|
DROP TABLE t1; |
10.4 fb01193c |
mysqltest: At line 13: query 'ALTER TABLE t1 MODIFY b TEXT' failed: 4029: Expression for field `DB_ROW_HASH_1` is refering to uninitialized field `DB_ROW_HASH_1`
|
Attachments
Issue Links
- is caused by
-
MDEV-371 Unique indexes for blobs
- Closed
- relates to
-
MDEV-18708 Server crash in Item_field::register_field_in_read_map upon modifying column into a blob
- Closed
-
MDEV-18709 Server crash or ASAN heap-buffer-overflow in create_index upon modifying column into a blob
- Closed