mariadb/mysql-test/suite/innodb
Thirunarayanan Balathandayuthapani 7afee25b08 MDEV-35115 Inconsistent Replace behaviour when multiple unique index exist
- Replace statement fails with duplicate key error when multiple
unique key conflict happens. Reason is that Server expects the
InnoDB engine to store the confliciting keys in ascending order.
But the InnoDB doesn't store the conflicting keys
in ascending order.

Fix:
===
- Enable HA_DUPLICATE_KEY_NOT_IN_ORDER for InnoDB storage engine
only when unique index order is different in .frm and innodb dictionary.
2024-11-08 16:46:41 +05:30
..
include mtr: remove innodb combinations 2024-05-05 21:37:08 +02:00
r MDEV-35115 Inconsistent Replace behaviour when multiple unique index exist 2024-11-08 16:46:41 +05:30
t MDEV-35115 Inconsistent Replace behaviour when multiple unique index exist 2024-11-08 16:46:41 +05:30
disabled.def MDEV-32725 innodb.import_update_stats accesses uninitialized ib_table->stat_n_rows 2023-12-04 10:30:39 +01:00