MySQL Bugs: #36503: Will Break Replication on different databases due to bug reading the my.ini

Bug #36503	Will Break Replication on different databases due to bug reading the my.ini
Submitted:	5 May 2008 10:50	Modified:	8 Oct 2008 12:47
Reporter:	Karlheinz Meier	Email Updates:
Status:	To be fixed later
Category:	MySQL Administrator	Severity:	S2 (Serious)
Version:	1.1.12	OS:	Microsoft Windows
Assigned to:	Mike Lischke	Target Version:
Tags:	replication, administrator
Triage:	D2 (Serious)

Description:
The Manual for replication reads : You have to use use multiple instances of the
replicate-do-db statement, as database-names can have commas. 

So if you want to replicate 2 dbs, you would write into the my.ini :

replicate-do-db=db1
replicate-do-db=db2

The MySQL-Administrator somehow seems not to correctly process this statement.
It just uses the first statement of "replicate-do-db" for the field in the
replication-tab.
The 2nd database is ignored.

If it only would be ignored, the bug would not be serious.
As soon as you change something in the administrator and acknowledge the change,
the administrator (!) OVERWRITES (!) the 2nd statement.

So after changing something the statement in my.ini reads :

replicate-do-db=db1
replicate-do-db=db1

voila, the 2nd database is not replicated anymore as soon as you restart the slave prcess
or the mysql server

How to repeat:
edit my.ini with text editor :

append : 

replicate-do-db=db1
replicate-do-db=db2

save file

open mysql administrator
open "replication"-tab
you will see that only one database is listed

change something
acknowledge the change

use the text-editor to open the my.ini

look for the replicate-do-db - statement

Suggested fix:
Mysql administrator should somehow leave the 2nd replicate-do-db - statement alone.
Or it should loop through all the replicate-do-db - statements and make a
replication-line in the gui for every single statement

Thank you for the bug report.

Due to the way the ini file is parsed, written and presented in the GUI there would be a
significant effort to fix this problem. Since this feature is planned to be implemented
in MySQL Workbench the fix is deferred.

Due to the way the ini file is parsed, written and presented in the GUI there would be a
significant effort to fix this problem. Since this feature is planned to be implemented
in MySQL Workbench the fix is deferred.

What is the status of this bug, Mike?  I am planning to replicate two dbs (db1 and db2
from the above exmaple) with wild-do statements.  Thanks

With the upcomming MySQL Workbench 5.2 beta we have included the ability to properly work
with the server configuration files and also have added dump and restore functionality
using the standard mysqldump tool. Please see http://wb.mysql.com for more information.