Bug #82270 Synchronise model to database tries to alter columns identical expression
Submitted: 18 Jul 2016 14:02 Modified: 26 Jul 2016 9:29
Reporter: Emmanuel Borlet Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:6.3.7 OS:Any
Assigned to: CPU Architecture:Any

[18 Jul 2016 14:02] Emmanuel Borlet
Description:
Description:
When synchronising two models, Workbench suggests altering columns that are identical in database and model
I'm on a 
- Mac OS X Yosemite
- Server version: 5.6.31-log Source distribution (via macports.org)
- MySQL Workbench 6.3.7

How to repeat:
Exemple table 
CREATE TABLE IF NOT EXISTS `_base` (
  `id` INT(10) UNSIGNED NOT NULL AUTO_INCREMENT,
  `date_created` TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6),
  `date_updated` TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6),
  PRIMARY KEY (`id`))
ENGINE = InnoDB
DEFAULT CHARACTER SET = utf8

log generated by the sync :

ALTER TABLE `_base` 
CHANGE COLUMN `date_updated` `date_updated` TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6) ;

Forever 

Suggested fix:
It stop when i set in the model (note that i have removed (6) at the end)
 `date_updated` `date_updated` TIMESTAMP(6) NOT NULL DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP ;

I find this by apply in the reverse sens, but i what to keep my (6) at the end
[26 Jul 2016 9:29] MySQL Verification Team
Hello Emmanuel Borlet,

Thank you for the report.
Observed this with WB 6.3.7 on Win7.

Thanks,
Umesh