mariadb/storage
Annamalai Gurusami 98b18c5971 Bug #20442523 CRASH WHEN CREATE TABLE VIOLATES FOREIGN KEY CONSTRAINT
Problem:

This is a coding mistake during error handling.  When the specified foreign
key constraint is wrong because of data type mismatch, the resulting
foreign key object will not have valid foreign->id (it will be NULL.)

Solution:

While removing the foreign key object from dictionary cache during error
handling, ensure that foreign->id is not null before using it.

rb#8204 approved by Sunny.
2015-03-03 17:57:08 +05:30
..
archive Description: When we execute a correlated subquery on an 2014-04-10 11:10:31 +05:30
blackhole Merge 5.5.24 back into main 5.5. 2012-05-07 22:20:42 +02:00
csv Updated/added copyright headers 2012-02-16 10:48:16 +01:00
example Updated/added copyright headers 2014-01-06 10:52:35 +05:30
federated Bug #12671631 CREATE TABLE .. LIKE .. FEDERATED TABLE 2015-01-28 09:43:34 +05:30
heap Bug#18463911 : SERVER CRASHES ON CREATING A TEMP TABLE WITH 2014-06-26 10:08:55 +05:30
innobase Bug #20442523 CRASH WHEN CREATE TABLE VIOLATES FOREIGN KEY CONSTRAINT 2015-03-03 17:57:08 +05:30
myisam Changing the copyright headers a bit to be complaint with the standards 2014-08-27 16:06:50 +02:00
myisammrg Updated/added copyright header. Added line "use is subject to license terms" 2014-02-17 18:19:04 +05:30
ndb Updated/added copyright header. Added line "use is subject to license terms" 2014-02-17 18:19:04 +05:30
perfschema Updated/added copyright header. Added line "use is subject to license terms" 2014-02-17 18:19:04 +05:30