Jan Lindström 8cc9751165 MDEV-7538: Wrong constraint (TINYINT or MEDIUMINT and INT) ... causes server crash Analysis: If wrong data types used on foreign constraint there was possibility that foreign->id is NULL when incorrect foreign constraint was removed from the dictionary cache. Fix: Add guard foreign->id != NULL before trying to lookup or remove the foreign constraint from dictionary cache. Tested using user database where problem was repeatable.		2015-02-04 14:40:46 +02:00
..
dict0boot.c	Fixing the bug 16919882 - WRONG FSF ADDRESS IN LICENSES HEADERS	2013-06-10 22:29:41 +02:00
dict0crea.c	Bug #18806829 OPENING INNODB TABLES WITH MANY FOREIGN KEY REFERENCES IS	2014-06-10 09:35:50 +05:30
dict0dict.c	MDEV-7538: Wrong constraint (TINYINT or MEDIUMINT and INT)	2015-02-04 14:40:46 +02:00
dict0load.c	Fix missing UNIV_INTERN on dict_table_check_foreign_keys().	2014-10-20 10:50:10 +02:00
dict0mem.c	Bug #18806829 OPENING INNODB TABLES WITH MANY FOREIGN KEY REFERENCES IS	2014-06-10 09:35:50 +05:30