information. See WL#6379 for the foreign key table definitions.
lock the child (and thus the FK definitions) when altering the parent.
define quite strict constraints that checks the validity of e.g. fk names.
should be implemented as part of this WL. The decision was keep current behaviour.
rows in mysql.foreign_keys and mysql.foreign_key_column_usage to be removed.
mysql.foreign_key_column_usage to be updated with the new column name.
InnoDB still also has FKs stored in their internal dictionary.
the table name is legal (again matching current InnoDB implementation).
checks of the parent table when creating foreign keys (e.g. if parent exists).
table name and referenced column name are all limited to 64 characters.
Trying to use longer identifiers will give an error.
changes to the parent table. See I-3 below.
have issues retrieving the correct tuple from the dictionary.
applies for the referenced_table_name and referenced_column name fields.
also takes into account dropping of foreign keys and renaming of columns.