MySQL Bugs: #68191: MilliSecond Datetime not available as a datatype in MySQL Workbench

Bug #68191	MilliSecond Datetime not available as a datatype in MySQL Workbench
Submitted:	27 Jan 2013 19:33	Modified:	11 Jun 2013 23:03
Reporter:	Austin Kalb	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.4.5	OS:	MacOS
Assigned to:		CPU Architecture:	Any
Tags:	DATETIME MILLISECOND MS

Description:
DATETIME is the only available option for the date / time data type in MySql Workbench. DATETIME(n), where n is any integer is not accepted, and converts back to DATETIME.

How to repeat:
Try creating a column with the datatype DATETIME(6)

Thank you for the bug report. Could you please provide the result of the below sql command:

SHOW VARIABLES LIKE "%version%";

Thanks.

Information you requested:

Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 458
Server version: 5.6.9-rc MySQL Community Server (GPL)

Copyright (c) 2000, 2012, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql> SHOW VARIABLES LIKE "%version%";
+-------------------------+------------------------------+
| Variable_name           | Value                        |
+-------------------------+------------------------------+
| innodb_version          | 1.2.9                        |
| protocol_version        | 10                           |
| slave_type_conversions  |                              |
| version                 | 5.6.9-rc                     |
| version_comment         | MySQL Community Server (GPL) |
| version_compile_machine | x86                          |
| version_compile_os      | Win32                        |
+-------------------------+------------------------------+
7 rows in set (0.00 sec)

mysql>

Thank you for the feedback. Sorry I didn't notice you category is Modeling and not with SQL Editor an alive server. So verified as described.

http://bugs.mysql.com/bug.php?id=68870 duplicate of this one.

TIME(n) and TIMESTAMP(n) have the same problem

Fixed as of the upcoming MySQL Workbench 6.0.2 release, and here's the changelog entry:

Datetime with fractional seconds is now supported. Before, MySQL Workbench
would convert "DATETIME(n)" (where "n" is an integer) to "DATETIME". This
fix also applies to "TIMESTAMP(n)". 

Note that this option requires the
default target MySQL Server version set to "5.6", which is set with the
"Model", "Model Options" preference.

Thank you for the bug report.

Not sure this is fixed, still experiencing the same behaviour in versions 6.0.3 and 6.0.4.  Indeed, I can't even set a column as being just DATETIME - will only let me use DATE.

Problem still exist in 6.0.5.11166 downloaded today.
Mysql 5.6.12

Still not fixed in version 6.0.6.11184!

still not fixed in 6.0.9.11412 build 1170 community edition.

seems the problem is on the model, as reported in http://bugs.mysql.com/bug.php?id=70125.
it works if creating a new schema.

I have workbench6.3.3 and I have this problem.It used to work but suddenly it doesn't accept time() or timestamp().

It still isn't fixed. The model is fixed but as we all know, syncing the model can be buggy unless you delete the online schema first (wish I could do that automatically at this point). Anyway, the issue isn't with the model now, it's with the online interface... I don't know what to call it, the interface where you can run sql querys and view table contents, not the modeller or the weird screen that always pops up before it. DATETIME(6) will work if you do it fresh from the modeller... but if you do it from the interface I'm talking about it 100% isn't support, always pops back to DATETIME. Man this tool is almost very useful if it wasn't so buggy... time for rebuild.