Bug #110304 Workbench 8.0.32 does not synchronize TIMESTAMP(3) column definitions
Submitted: 8 Mar 2023 16:14 Modified: 9 Mar 2023 9:53
Reporter: Adrian Faur Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.32 OS:Windows
Assigned to: CPU Architecture:Any

[8 Mar 2023 16:14] Adrian Faur 
Description:
After changing DATETIME to TIMESTAMP(3), workbench does nor synchronize and keeps reporting model vs database mismatches for the changed columns. i.e,:

ALTER TABLE `clients`.`app_user` 
CHANGE COLUMN `LAST_UPDATE_DATETIME` `LAST_UPDATE_DATETIME` TIMESTAMP NOT NULL;

The correct ALTER command should be:

ALTER TABLE `eshark`.`app_user` 
CHANGE COLUMN `LAST_UPDATE_DATETIME` `LAST_UPDATE_DATETIME` TIMESTAMP(3) NOT NULL;

Forward engineer works OK, the columns are correctly defined as TIMESTAMP(3). However, because I am using workbench to incrementally generate scripts for database schema updates, I cannot use forward engineer method to update database without loosing existing database data.

How to repeat:
Create a table with a DATETIME column type, synchronize db changes, change column type to TIMESTAMP(3) and synchronize again: you will keep getting incorrect ALTER TABLE scripts as above.
[8 Mar 2023 16:20] Adrian Faur 
workbech synchronize dialog and related table definition

Attachment: snap0581.jpg (image/jpeg, text), 493.31 KiB.
[9 Mar 2023 9:53] MySQL Verification Team 
Hello Adrian,

Thank you for the bug report.
Imho this is duplicate of Bug #74617, please see Bug #74617.

Regards,
Ashwini Patil