Bug #46736 Synchronization fails
Submitted: 14 Aug 2009 17:48 Modified: 17 Sep 2009 4:48
Reporter: Johan Natt och Dag Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:5.1.16 & 5.2.2 alpha OS:Windows (XP, jre6, mysql 5.0.45)
Assigned to: CPU Architecture:Any
Tags: Synch, synchronization, synchronize model

[14 Aug 2009 17:48] Johan Natt och Dag
Description:
The synchronization only affects added and removed tables. Modified tables are not updated in either direction.

The diff overview shows several modification but the resulting script does not contain any ALTER TABLE statements.

Also, the catalog diff shows the difference, but they are not propagated. None of these differences generated any ALTER TABLE statements:

+--------------------------------------------+

| Catalog Diff Report                        |

+--------------------------------------------+

Table `f`.`academicorganization_has_positions` was modified

  attributes:

  - pack keys: 0 --> DEFAULT

  - row format:  --> DEFAULT

  __

Table `f`.`academicorganization_has_users` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`academicorganization` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`actions` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`album` was modified

  columns:

  - modified column Visible

  __

Table `f`.`i18n` was modified

  columns:

  - modified column Type

  __

  indices:

  - added index fk_I18n_SettingCategories1 with columns: Id

  __

Table `f`.`items` was modified

  columns:

  - modified column Available

  __

  indices:

  - added index PRIMARY with columns: Id

  - removed index PRIMARY

  __

Table `f`.`languages` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`maritalstatuses` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`media` was modified

  columns:

  - added column ParentMediaId of type BINARY

  - added column ParentMediaId of type INT

  - removed column FileSize

  __

  indices:

  - added index fk_Media_Media2 with columns: ParentMediaId

  __

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`memberstatuses` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`organizations_has_roles` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`organizations` was modified

  columns:

  - modified column IsLodge

  __

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`pagerevisions` was modified

  indices:

  - added index PRIMARY with columns: Revision, PageId

  - removed index PRIMARY

  __

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`pages` was modified

  columns:

  - modified column Id

  __

  indices:

  - added index PRIMARY with columns: Id

  - removed index PRIMARY

  __

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`payments` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`phonenumbertypes` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`post` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`privileges` was modified

  indices:

  - added index PRIMARY with columns: Id

  - removed index PRIMARY

  __

Table `f`.`roles_has_mailinglists` was modified

  columns:

  - modified column MandatorySubscription

  __

Table `f`.`roles_has_users` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`roles` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`settingcategories` was modified

  columns:

  - modified column DescriptionId

  __

Table `f`.`users_has_actions` was modified

  attributes:

  - pack keys:  --> 0

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_emailaddresses` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_items` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_locations` was modified

  attributes:

  - pack keys:  --> 0

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_mailinglists` was modified

  attributes:

  - pack keys:  --> 0

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_medals` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_phonenumbers` was modified

  indices:

  - added index PRIMARY with columns: UsersId, PhoneNumber

  - removed index PRIMARY

  __

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`users_has_ranks` was modified

  attributes:

  - pack keys:  --> 1

  - row format:  --> DEFAULT

  __

Table `f`.`users` was modified

  columns:

  - added column AddTest of type VARCHAR

  __

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`assettypes` was modified

  attributes:

  - pack keys:  --> 0

  - row format:  --> DEFAULT

  __

Table `f`.`events` was modified

  columns:

  - modified column Active

  __

Table `f`.`locations` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`positions` was modified

  attributes:

  - row format:  --> DEFAULT

  __

Table `f`.`settings` was modified

  columns:

  - added column SettingCategoriesId of type BINARY

  __

  indices:

  - added index fk_Settings_SettingCategories1 with columns: SettingCategoriesId

  __

Table `f`.`users_has_settings` was modified

  attributes:

  - pack keys:  --> 0

  - row format:  --> DEFAULT

  __

----------------------------------------------

End of MySQL Workbench Report

How to repeat:
Unable to reproduce :-(

1. Create 40 tables with relations.
2. Forward engineer
3. Edit away....
4. Synch

Suggested fix:
Code review the model synchronization algorithm.
[17 Aug 2009 4:48] Susanne Ebrecht
I am not able to reproduce this.

Please provide your model.
[17 Sep 2009 23: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".