Bug #64877 Synchronize With Any Sources doesn't work
Submitted: 5 Apr 2012 13:34 Modified: 10 Jun 2012 19:28
Reporter: Van Stokes Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.39 OS:Linux (Ubuntu 11.10 x86_64)
Assigned to: CPU Architecture:Any
Tags: diff, workbench

[5 Apr 2012 13:34] Van Stokes 
Description:
The Synchronize With Any Source does not work properly.

I have reversed engineered an existing database running on MySQL 5.5.22. I made alterations to tables and attempted to syncrhonize the changes via "Synchronize With Any Source".

The "Differences" found includes dropping and re-creating the database and dropping and recreating the tables. There are NO "ALTER" commands found. Furthemore, it shows that action is requires on ALL tables.

The source and destination show up as "N/A". See attached screen shot.

How to repeat:
1. Reverse Engineer
2. Alter a table
3. Synchronize With Any Source

I am wondering if the problem is because the database has underscores (_) in the name. I notice that in several areas of WB that the underscore is being removed from database and table names.

Suggested fix:
Actually make it work?
[5 Apr 2012 13:35] Van Stokes 
Screenshot of WB showing differences

Attachment: Screenshot at 2012-04-05 09:31:55.png (image/png, text), 250.22 KiB.
[24 Apr 2012 20:06] MySQL Verification Team 
Please try version 5.2.39. Thanks.
[25 Apr 2012 14:28] Van Stokes 
Same result in 5.2.39.
BTW, you should actually try looking into the problem instead of using a canned response every time a new release is made available.
[26 Apr 2012 18:14] Van Stokes 
Synchronise Model with Database STILL does not work. This application is all but useless now.

Target server is: MySQL 5.5.23-log x64 on Linux/Ubuntu.
[10 May 2012 19:28] Armando Lopez Valencia 
Hello Van.
Would you mind provide us with a Model/dump where you can reproduce this issue?
Thanks.
[11 Jun 2012 1:00] Bugs System 
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".