We upgraded from 5.2.17.Final to 5.4.32.Final and discovered an issue with violation of foreign key constraints in MySQL InnoDB tables running 5.7.mysql_aurora.2.09.2. We discovered in the 5.4 Migration Guide that we can revert the behavior introduced in 5.3 with the disable_delayed_identity_inserts property and that we should report our use case.
If you find you need to use this configuration setting, be sure to report the mapping to us in a JIRA issue so that we can review it and determine if the mapping corner case should be included in our algorithm since the configuration setting is meant to bridge behavior support for this across a few releases.
An example of our logged error:
The table schemas in question (with extraneous details omitted):
|