Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Fixed
-
10.3.2
Description
--source include/have_innodb.inc
|
|
CREATE TABLE t1 (pk VARCHAR(3) PRIMARY KEY) ENGINE=InnoDB; |
INSERT INTO t1 VALUES ('foo'); |
ALTER TABLE t1 ADD COLUMN f INT; |
UPDATE t1 SET f = 1; |
--error ER_DUP_ENTRY
|
INSERT INTO t1 VALUES ('foo',NULL); |
|
# Cleanup
|
DROP TABLE t1; |
The test fails on INSERT, because it actually succeeds instead of producing the expected ER_DUP_ENTRY.
Attachments
Issue Links
- blocks
-
MDEV-14840 Assertion `!log->same_pk' failed in row_log_table_apply_delete
- Closed
- is caused by
-
MDEV-11369 Instant add column for InnoDB
- Closed
- is duplicated by
-
MDEV-14473 Assertion `rec_get_trx_id(rec, clust_index) < trx->id' failed in row_merge_read_clustered_index on ADD FULLTEXT KEY
- Closed
-
MDEV-14897 After UPDATE of instant ADD COLUMN, PRIMARY KEY accepts duplicates
- Closed
- relates to
-
MDEV-14068 Assertion `0' failed in row_sel_get_clust_rec_for_mysql(row_prebuilt_t*, dict_index_t*, const rec_t*, que_thr_t*, const rec_t**, ulint**, mem_heap_t**, const dtuple_t**, mtr_t*)
- Closed