Bug #104094 MySQL Workbench Does't Recognize or Produce Precision () (n) on DATETIME Columns
Submitted: 23 Jun 2021 18:26 Modified: 25 Jun 2021 17:55
Reporter: Bill Rebey Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.25 OS:Windows
Assigned to: CPU Architecture:Any

[23 Jun 2021 18:26] Bill Rebey
Description:
A column defined in the GUI/Model with a DATETIME data type, and a precision, such as (3), generates SQL change script without the precision.

DATETIME(6) will result in a column being defined as just DATETIME.

Also, changing the precision value, removing it, or adding it where it wasn't before, is not recognized as a change, and no code at all is generated for the change.

How to repeat:
Happens every time.

Suggested fix:
Make the code generator recognize precision on the DATETIME data type.
[23 Jun 2021 20:45] MySQL Verification Team
Please provide the WorkBench version, server version which is connected to and attach the wb.log. Thanks.
[24 Jun 2021 13:40] Bill Rebey
Per request, version of Workbench and Server are both 8.0.25.  

wb.log attached.
[24 Jun 2021 14:37] MySQL Verification Team
Creating Table

Attachment: bug104094-1.png (image/png, text), 324.14 KiB.

[24 Jun 2021 14:38] MySQL Verification Team
Show Create Table

Attachment: bug104094-2.png (image/png, text), 67.33 KiB.

[24 Jun 2021 14:40] MySQL Verification Team
Thank you for the feedback. I couldn't repeat, see prior attached screen-shots.
[24 Jun 2021 16:35] Bill Rebey
DateTime precision goes missing...

Attachment: MySqlWbDatetime.png (image/png, text), 51.06 KiB.

[24 Jun 2021 16:36] Bill Rebey
I just attached a screen shot that show the error on my end.

It's clearly failing for me, while it works for you.

So now what?  What can we do to further trouble-shoot this?
[25 Jun 2021 12:15] MySQL Verification Team
Hello Bill Rebey,

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

Regards,
Ashwini Patil
[25 Jun 2021 17:55] Bill Rebey
Ok, so per your suggestion, I looked at bug #74617.

I agree, it does sound like it's the same problem in general.

So what now?  This has been a reported bug for SEVEN YEARS now.  The original by was reported in 2014.  

Rhetorically, I'll as "Why isn't this fixed yet?", but more practically, I'll ask "What do I need to do to get this fixed?"