MySQL Bugs: #54169: replication breaks when doing forward engineer or synchronize

Bug #54169	replication breaks when doing forward engineer or synchronize
Submitted:	2 Jun 2010 8:17	Modified:	4 Jul 2010 17:00
Reporter:	Markus Warg	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.20 OSS Beta	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Forward engineering and Model Synchronization break existing mysql replications.

How to repeat:
Make your database design in Workbench, then set up two MySQL Servers, one master and one slave. Forward engineer your design to the master db.

Replication breaks, because of the create table `db`.`name` style SQL.

Same for Synchronize Model when the master contains real data and replication is productional.

Suggested fix:
Make workbench issue "regular" use db, create/drop/alter style SQL.

The target mysql server is a standard Debian 5.0.51a package listed as 5.0.51a-24+lenny3.

you can disable the generation of schema-qualifiers in forward engineering wizard on options page which would solve one problem, if i'm not mistaken.
another problem though is that mysql workbench in its current version only support one synchronization target, so synchronizing your model to two different dbs doesn't work. this feature is on our roadmap for future versions.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/112692

3694 John David Duncan	2010-07-01
      Fix double-checked locking that was found during a code review for 
      bug#54169.  This may not fix the bug (which I have not yet been able to 
      reproduce) but is the right thing to do nonetheless.

Please disregard previous patch (submitted to the wrong bug).

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".