Bug #36174 Synchronize does not honour (or permitting selection of) excluded objects
Submitted: 17 Apr 2008 9:10 Modified: 1 Jun 2013 22:34
Reporter: Martin Gara Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.0.19 SE rev 3067 OS:Windows (Win2K)
Assigned to: CPU Architecture:Any

[17 Apr 2008 9:10] Martin Gara
Description:
Synchronize attempts to synchronise all database objects including those that will generate an issue.

How to repeat:
If you forward engineer from Workbench you have the option to exclude unwanted database objects.
If you subsequently Synchronize the database, Workbench will not remember what was previously excluded - this can result in the target database being dropped with no replacement.

Suggested fix:
Allow the Exclusion Dialog to be accessed when performing a synchronisation.
[17 Apr 2008 13:02] MySQL Verification Team
Thank you for the bug report.
Create table1 and table2, both with 3 columns. Forward engineer excluding
table2. Alter table1 adding one more column and after that Synchronize.
[18 Apr 2008 14:04] Johannes Taxacher
workaround for the meantime is to adjust synchronization on the "Diff Tree Page" of the wizard. double-klicking on the green arrow between mapped objects changes the way of handling the sync for each object seperately. 

there are three possible settings:
---->   sync the difference to database (change object in DB)
<-x->   don't sync this object
<----   sync the difference back to model (change object in Model)
[1 Jun 2013 22:34] Alfredo Kojima
Duplicate of Bug #63175