Bug #66364 MySQL WB Synchronize marks BOOL as different from TINYINT(1)
Submitted: 13 Aug 2012 23:10 Modified: 13 Jun 2013 23:52
Reporter: David Dykstra Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.41, 5.2.42 OS:Mac OS X (10.7.4)
Assigned to: CPU Architecture:Any
Tags: BOOL, synchronize, Tinyint, workbench

[13 Aug 2012 23:10] David Dykstra
When synchronizing my model with my schema, the synchronization code converts BOOL to TINYINT which is great however, in generating the diff it mark BOOL and TINYINT as a change even though BOOL is synonymous with TINYINT

How to repeat:
Make table with column BOOL, synchronize with schema, and then run synchronize again. Or create the model after creating the database, in the schema make a column of type TINYINT, and in the model mark it as BOOL, run synchronize.

Suggested fix:
Mark both in generating difference as being the same.
[19 Aug 2012 16:54] Valeriy Kravchuk
With 5.2.42 I see that "empty" SQL in generated upon second and subsequent attempts to synchronize. But Database > Generate Catalog Diff Reports ... still says that BOOL column is modified when I compare model to the live database. Something to fix for sure.
[13 Jun 2013 23:52] Philip Olson
Fixed as of the upcoming MySQL Workbench 6.0.2 public beta release, and here's the changelog entry:

When converting a "BOOL" to a "TINYINT(1)" when synchronizing a model with a
schema, the synchronization diff would continue to claim the two were

Thank you for the bug report.