Bug #51765 Comment column in synchronization
Submitted: 5 Mar 2010 10:46 Modified: 11 May 2010 14:17
Reporter: Marc Fret Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.16 Beta OS:Any (Snow Leopard)
Assigned to: Alexander Musienko CPU Architecture:Any
Tags: comments

[5 Mar 2010 10:46] Marc Fret 
Description:
if you put a comment on a column.
WorkBench found always a difference between the model and database

How to repeat:
Add a comment on a column, then synchronize the schema and database :

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

ALTER TABLE `diod`.`equipement` CHANGE COLUMN `Statut` `Statut` TINYINT(1) NULL DEFAULT 1 COMMENT 'test'  ;

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

The synchronizations are still differences between the database and model :

SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0;
SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0;
SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='TRADITIONAL';

ALTER TABLE `diod`.`equipement` CHANGE COLUMN `Statut` `Statut` TINYINT(1) NULL DEFAULT 1 COMMENT 'test'  ;

SET SQL_MODE=@OLD_SQL_MODE;
SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS;
SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS;

if you choose "Update Model", in Workbench your comment is now 'tes

synchronizations are following good
[10 Mar 2010 8:13] Susanne Ebrecht 
Bug #51871 is set as duplicate of this bug here.
[19 Mar 2010 13:46] Johannes Taxacher 
Bug #52209 has been marked as duplicate of this one
[20 Mar 2010 8:35] Leif Inge Sandberg 
Just a note; bug #51871 is a duplicate with additional information - the bug affects table comments as well.

The comparison feature is an excellent one, given that it works properly :-) It will add greatly to the usefulness of Workbench when this bug is fixed.
[16 Apr 2010 15:27] Valeriy Kravchuk 
Bug #51886 was marked as a duplicate of this one.
[19 Apr 2010 19:10] blawat konrad 
i have the same problem :/

it's very irritable bug :/
[10 May 2010 22:07] Johannes Taxacher 
fix confirmed in repository
[11 May 2010 14:17] Tony Bedford 
An entry has been added to the 5.2.21 changelog:

Any columns that contained a comment would be marked for change when synchronizing the model with the live database.