View Revisions: Issue #3892

All RevisionsBack to Issue
Summary 0003892: MySQL Version 8 returning error code 1216 when foreign key constraint is violated (used to be 1452)
Revision 2019-03-22 18:08 by pmarzullo
Steps To Reproduce 1. Run Symmetric against MySQL version 8 (at least in the target).
2. Set up tables with foreign key constraints.
3. Set up synchronization.
4. Set up data to allow a foreign key constraint violation in the target database.
5. Create the data change to create the foreign key constraint violation in the target database.
6. SymmetricDS should not be able to resolve the foreign key constraint because the database error code returned by the database is 1216 instead of 1452.

DDL specified in additional information.
Revision 2019-03-22 17:15 by pmarzullo
Steps To Reproduce 1. Run Symmetric against MySQL version 8 (at least in the target).
2. Set up tables with foreign key constraints.
3. Set up synchronization.
4. Set up data to allow a foreign key constraint violation in the target database.
5. Create the data change to create the foreign key constraint violation in the target database.
6. SymmetricDS should not be able to resolve the foreign key constraint because the database error code returned by the database is 1216 instead of 1452.

TODO: Create DDL and insert here to make it easy to recreate the problem.