Bug #29064 | MySQL replication - database not marked for replication also gets replicated | ||
---|---|---|---|
Submitted: | 13 Jun 2007 7:13 | Modified: | 13 Jun 2007 8:32 |
Reporter: | Jayadevan M | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.0.41 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[13 Jun 2007 7:13]
Jayadevan M
[13 Jun 2007 7:26]
Sveta Smirnova
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://dev.mysql.com/doc/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Please read carefully at http://dev.mysql.com/doc/refman/5.0/en/replication-options.html how option --replicate-do-db works
[13 Jun 2007 8:32]
Jayadevan M
Hi, User xyz is not found in MYSQL3. That is fine. I understand that. My query was - Why is abc found in MYSQL3? Creating a user, did not change the data in mynewdb in anyway. I tested further. I tried something else - I did a 'use newdb' and created a new database. Now this db got replicated only to MYSQL2 - behaviour is as expected. It did not get replicated to MYSQL3. I hope it is clear. The bug is not that a user did not get replicated, the bug is that a user did get replicated.