Bug #81745 DROP TABLE IF EXISTS brake replication master-slave replication

• Submitted: 7 Jun 2016 5:32
• Modified: 7 Jun 2016 6:03
• Reporter: ATUL SINGH
• Status: Duplicate
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 5.7.12
• OS: CentOS (6.5)
• CPU Architecture: Any

[7 Jun 2016 5:32] ATUL SINGH

Description:

If a replica has replication filters on a given database and DROP TABLE IF EXISTS is issued 
on a table that holds a key being used as Foreign Key by another table the statement will fail as expected with error:

ERROR 1217 (23000): Cannot delete or update a parent row: a foreign key constraint fails

How to repeat:
binlog-do-db= mamcdb_hd
binlog-do-db= lstconfig_hd
log_slave_updates=1
enforce_gtid_consistency=true
gtid_mode=on
binlog_format=mixed
binlog_gtid_simple_recovery=on

[7 Jun 2016 6:03] Umesh Shastry

Please do not submit the same bug more than once. An existing bug report Bug #81744 already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.