Bug #53747 Syncronize single BIT field
Submitted: 18 May 2010 12:03 Modified: 15 Jun 2010 15:41
Reporter: Daniel Bradley Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.21 OSS RC Revision 5918 OS:Windows (XP SP3)
Assigned to: Alexander Musienko CPU Architecture:Any
Tags: syncronize bit

[18 May 2010 12:03] Daniel Bradley
Description:
When syncronizing changes to the database collumns defined as datatype BIT are always evaluated as modified due to the server automatically appending "(1)".

Workbench contains the option "BIT" and this is not just directly typed in.

How to repeat:
1) Create a column in a table and select data type "BIT".
2) Push changes to the database through either forward engineer or synchronize.
3) Synchronize changes again having made no changes and the new column will be modified again.
4) Change the column data type to "BIT(1)" and re-synchronize changes and the column will not be updated.

Suggested fix:
Either change the list to be "BIT(1)" rather than "BIT", or preferably add logic to the DIFF which evaluates "BIT" and "BIT(1)" as equal.
[18 May 2010 12:16] Daniel Bradley
Also applies to the CHAR data type: fixed when changed to CHAR(1).
[14 Jun 2010 21:44] Johannes Taxacher
fix confirmed in repository
[15 Jun 2010 15:41] Tony Bedford
An entry has been added to the 5.2.23 changelog:

Columns defined as BIT appeared as requiring synchronization, even if no changes had been made.