Sergei Golubchik 0d8bd7cc3a MDEV-18428 Memory: If transactional=0 is specified in CREATE TABLE, it is not possible to ALTER TABLE ... * be strict in CREATE TABLE, just like in ALTER TABLE, because CREATE TABLE, just like ALTER TABLE, can be rolled back for any engine * but don't auto-convert warnings into errors for engine warnings (handler::create) - this matches ALTER TABLE behavior * and not when creating a default record, these errors are handled specially (and replaced with ER_INVALID_DEFAULT) * always issue a Note when a non-unique key is truncated, because it's not a Warning that can be converted to an Error. Before this commit it was a Note for blobs and a Warning for all other data types.		2021-01-11 21:54:47 +01:00
..
include	MDEV-16952 Introduce SET GLOBAL innodb_max_purge_lag_wait	2020-10-27 15:47:18 +02:00
r	MDEV-18428 Memory: If transactional=0 is specified in CREATE TABLE, it is not possible to ALTER TABLE	2021-01-11 21:54:47 +01:00
t	MDEV-24346 valgrind error in main.precedence	2020-12-19 11:44:42 +01:00
disabled.def	MDEV-23339 innodb_force_recovery=2 may still abort the rollback of recovered transactions	2020-07-30 09:24:36 +03:00