Bug #9602 | replicate-do-db does not check database prefix on queries | ||
---|---|---|---|
Submitted: | 4 Apr 2005 10:49 | Modified: | 4 Apr 2005 14:10 |
Reporter: | Balint Toth | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 4.0.18, for pc-linux-gnu (i686) | OS: | Linux (Debian Linux 3.0) |
Assigned to: | CPU Architecture: | Any |
[4 Apr 2005 10:49]
Balint Toth
[4 Apr 2005 14:10]
MySQL Verification Team
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: From the MySQL manual: Tells the slave to restrict replication to statements where the default database (that is, the one selected by USE) is db_name. To specify more than one database, use this option multiple times, once for each database. Note that this does not replicate cross-database statements such as UPDATE some_db.some_table SET foo='bar' while having selected a different database or no database. If you need cross-database updates to work, make sure that you have MySQL 3.23.28 or later, and use --replicate-wild-do-table=db_name.%. Please read the notes that follow this option list. An example of what does not work as you might expect: If the slave is started with --replicate-do-db=sales and you issue the following statements on the master, the UPDATE statement is not replicated: USE prices; UPDATE sales.january SET amount=amount+1000;