Bug #42149 | Synchronization nearly unusable | ||
---|---|---|---|
Submitted: | 16 Jan 2009 8:53 | Modified: | 26 Jun 2009 10:42 |
Reporter: | Jan Juricek | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S1 (Critical) |
Version: | 5.0.30 | OS: | Windows |
Assigned to: | Alexander Musienko | CPU Architecture: | Any |
Tags: | CHECKED |
[16 Jan 2009 8:53]
Jan Juricek
[16 Jan 2009 8:54]
Jan Juricek
SQL produced by SQL Diff tree
Attachment: result-diff-query.sql (text/x-sql), 7.25 KiB.
[16 Jan 2009 8:55]
Jan Juricek
Shema screenshot part 1
Attachment: schema01.JPG (image/jpeg, text), 121.33 KiB.
[16 Jan 2009 8:55]
Jan Juricek
Shema screenshot part 2
Attachment: schema02.JPG (image/jpeg, text), 145.44 KiB.
[16 Jan 2009 8:56]
Jan Juricek
Shema screenshot part 3
Attachment: schema03.JPG (image/jpeg, text), 120.11 KiB.
[16 Jan 2009 8:56]
Jan Juricek
Shema screenshot part 4
Attachment: schema04.JPG (image/jpeg, text), 114.67 KiB.
[16 Jan 2009 8:56]
Jan Juricek
Shema screenshot part 5
Attachment: schema05.JPG (image/jpeg, text), 109.10 KiB.
[16 Jan 2009 8:56]
Jan Juricek
Shema screenshot part 6
Attachment: schema06.JPG (image/jpeg, text), 110.02 KiB.
[16 Jan 2009 8:57]
Jan Juricek
Test model after second sync
Attachment: test.mwb (application/octet-stream, text), 3.88 KiB.
[26 Jan 2009 16:08]
Susanne Ebrecht
Many thanks for pointing this out. It seems there is something more broken at the sync from database into model scenario. Verified by using a very simple design. Our developers will check this.
[12 Mar 2009 7:40]
Jonas Stenberg
I also have this problem since I consider the database to be the master. The Workbench application is for me just a way to print a nice map of the database. But it really can't handle that task in a satisfying way. I NEVER want changes in the Workbench to be propagated to the database. I would like to add the following disturbing behaviour to this bug: If I drop tables or views in the database and then synchronize with the Workbench model they are not deleted in the Workbench model.
[16 Mar 2009 14:03]
Susanne Ebrecht
Still very mystic what happens during synchronisation. When you explicit say that you don't want to synchronise some stuff it will be synchronised anyway.
[16 Mar 2009 14:06]
Susanne Ebrecht
Still very mystic what happens during synchronisation. When you explicit say that you don't want to synchronise some stuff it will be synchronised anyway.
[27 May 2009 17:49]
Dan Diman
Just another comment to confirm this behavior. I created a model, and synchronized it to an empty live schema. If I I make no changes to either the live schema or the model in Workbench, the "Synchronize..." menu selection idnetifies many many changes it beleives need to be made.
[24 Jun 2009 20:03]
Johannes Taxacher
There have been several fixes to the synchronization routines in version 5.1. the fixes will be included in 5.1.15
[26 Jun 2009 10:42]
Tony Bedford
An entry has been added to the 5.1.15 changelog: MySQL Workbench Syncronize Model feature had unexpected behavior. For example, synchronizing the model with the live database would cause changes to the database, even if this was not desired. Also, if tables were dropped in the live database, and the model synchronized, the changes to the live database were not reflected in the model. Further, if a model was created and synchronized to an empty schema in the live database, when synchronization took place again, MySQL Workbench would indicate many changes were required, even if no changes had been made to the model or database.