MySQL Bugs: #77106: Workbench attempts to make DB changes after selecting Update Model for all.

Bug #77106	Workbench attempts to make DB changes after selecting Update Model for all.
Submitted:	20 May 2015 15:44	Modified:	18 Jul 2015 21:32
Reporter:	Sterling Cox	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Migration	Severity:	S3 (Non-critical)
Version:	6.2.4.12437 build 2426	OS:	MacOS (10.10.3)
Assigned to:		CPU Architecture:	Any
Tags:	migration, synchronization, workbench

Description:
After altering a database directly and attempting to incorporate those changes into a Workbench model using the Database/Synchronize Model dialog, when all differences are selected in the list of differences and the button "Update Model" is pressed, causing all differences to be represented by yellow left-facing arrows indicating the model will be updated, when the "Continue" button is pressed, the "Preview Database Changes to be Applied" dialog shows a script attempting to change the database to match the model - the opposite of what was asked.

Ticking the "Skip DB changes and update model only" check-box, interestingly, does result in the desired behavior in this case.

See https://imgur.com/a/aVDgX

How to repeat:
1. Reverse engineer a model from a database
2. Alter a table in the database directly (add a column)
3. select the Database/Synchronize Model dialog in Workbench
4. select all differences (or everything) on the entity list and clike the "Update Model" button so all Updates are represented by yellow left-facing arrows
5. click Continue
6. Marvel at the proposed "alter table drop column" statements.

Selected "Update Model" on all

Attachment: workbench bug 1.jpg (image/jpeg, text), 110.82 KiB.

Workbench tries to update DB

Attachment: workbench bug 2.jpg (image/jpeg, text), 106.69 KiB.

Please try version 6.3.4. Thanks.

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".