MySQL Bugs: #80204: Error when trying to use Datatype TIMESTAMP()

Bug #80204	Error when trying to use Datatype TIMESTAMP()
Submitted:	29 Jan 2016 21:49	Modified:	31 Jan 2016 19:26
Reporter:	Filipus Klutiero	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	6.3.6	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
In Alter Table..., when selecting Datatype TIMESTAMP() and trying to switch to the next column, Workbench complains:
Could not set new data type
The given data type
TIMESTAMP()
contains errors and cannot be accepted. The previous value is kept instead.

And indeed, TIMESTAMP() is not kept.

This can be worked around by removing the parentheses.

This happens with MySQL 5.5, but I am under the impression that the server is not involved. It seems to be Workbench failing to verify one of its own suggestions.

How to repeat:
Open a table with Alter Table...
In the empty row, click on the Datatype column and choose "TIMESTAMP()"
Select the next column

Thank you for the bug report. You have the option to remove the parenthesis so you can have a column like:

ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,

or you type between the parenthesis so you can have a column like:

ts TIMESTAMP(6) DEFAULT CURRENT_TIMESTAMP(6) ON UPDATE CURRENT_TIMESTAMP(6)

I accept that some may not consider the error as a bug. I have reported the underlying issue in ticket #80209.

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

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