Bug #111078 Workbench 8.0.32 does not synchronize TIMESTAMP(3) column definitions
Submitted: 18 May 2023 17:56 Modified: 19 May 2023 7:20
Reporter: Adrian Faur Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:8.0.32 OS:Any
Assigned to: CPU Architecture:Any

[18 May 2023 17:56] Adrian Faur
Description:
Workbench does not synchronize Datetime or Timestamp column types if these column types are changed to a fractional seconds definition ( datetime(3), datetime(6), timestamp(3), timestamp(6) ). If changes are done manually by scripts like

ALTER TABLE `schema`.`table` 
CHANGE COLUMN `EVENT_START_DATETIME` `EVENT_START_DATETIME` DATETIME(3) NOT NULL ;

- database schema is changed, but when synchronizing back to model is not updated. 
- if we forward engineer schema manual changes are lost because they are not read back to model from database. so synch is lost.

How to repeat:
just modify a column table from datetime to datetime(3), or timestamp to timestamp(3) and synchronize.
[19 May 2023 7:20] 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