Bug #68870 Workbench model will not accept DATETIME(6) or TIMESTAMP(6) for a column
Submitted: 5 Apr 2013 0:09 Modified: 5 Apr 2013 3:11
Reporter: Ben Heath Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.47 OS:Windows (Win 7 x64)
Assigned to: CPU Architecture:Any

[5 Apr 2013 0:09] Ben Heath 
Description:
When attempting to configure a column as either DATETIME(6) or TIMESTAMP(6) an error message is displayed saying 
'The given data type

DATETIME(6)

contains errors and cannot be accepted. The previous value is kept instead.'

This occurs when attempting to add a new column or edit an existing column.  The same behaviour occurs in both the model overview screen and in the EER Diagram screen.

How to repeat:
Fairly simple, as per description (no code sample possible because the bug is centred on GUI behaviour)
[5 Apr 2013 0:13] Ben Heath 
Screenshot - DATETIME(6)

Attachment: MySQL_Workbench_Bug_01.PNG (image/png, text), 29.51 KiB.
[5 Apr 2013 0:13] Ben Heath 
Screenshot - TIMESTAMP(6)

Attachment: MySQL_Workbench_Bug_02.PNG (image/png, text), 38.81 KiB.
[5 Apr 2013 3:11] MySQL Verification Team 
Thank you for the bug report. Duplicate of http://bugs.mysql.com/bug.php?id=68191.
[4 Aug 2013 15:16] MySQL Verification Team 
http://bugs.mysql.com/bug.php?id=69924 duplicate of this one.
[23 Nov 2015 19:36] Olivier D 
This happens also to me... Instead I use int and I will change it later... Strange this issue is still not solved
[14 Jan 2016 17:15] shaun neal 
Fresh install of 5.7 and 6.3.3 from the website today.

Create new schema
Create new table
Try to use datetime or timestamp - nope - error
[12 May 2019 16:54] Fernando Alonso 
2019...I can't believe...the bug remains... Anyone know a workaround this fuck shit?

Thanks in advance