Details
Description
CREATE TABLE t1 (f TEXT UNIQUE); |
INSERT INTO t1 VALUES (NULL),(NULL); |
UPDATE t1 SET f = ''; |
SELECT * FROM t1; |
DROP TABLE t1; |
10.4 de20872331 |
MariaDB [test]> UPDATE t1 SET f = ''; |
Query OK, 2 rows affected (0.116 sec) |
Rows matched: 2 Changed: 2 Warnings: 0 |
 |
MariaDB [test]> SELECT * FROM t1; |
+------+ |
| f |
|
+------+ |
| |
|
| |
|
+------+ |
2 rows in set (0.000 sec) |
Reproducible on 10.4, 10.5.
INSERT of empty values returns ER_DUP_ENTRY as expected.
UPDATE from non-NULL values and UPDATE to non-empty values also returns ER_DUP_ENTRY.
Attachments
Issue Links
- is caused by
-
MDEV-371 Unique indexes for blobs
- Closed
- relates to
-
MDEV-23265 Assertion `!expl_lock || expl_lock->trx == arg->impl_trx' failed in lock_rec_other_trx_holds_expl_callback upon concurrent UPDATE with unique blobs
- Confirmed
-
MDEV-29199 Unique hash key is ignored upon INSERT ... SELECT into non-empty MyISAM table
- Closed
-
MDEV-29949 Unique blobs allow duplicate values upon concurrent INSERT
- Open