Bug #86906 Cannot edit foreign keys/indexes/view primary keys
Submitted: 3 Jul 2017 14:16 Modified: 4 Jun 2020 18:22
Reporter: Brian Leishman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.9 OS:Windows
Assigned to: CPU Architecture:Any

[3 Jul 2017 14:16] Brian Leishman 
Description:
If the default expression for a table is "NULL ON UPDATE CURRENT_TIMESTAMP(6)", loading the table in the table editor is quite broken.

Looks like it can't parse that string, so anything after that in the "show create table" doesn't get considered anymore, so you can't view current indexes or foreign keys, etc. Also, it shows up as "ON UPDATE CURRENT_TIMESTAMP()" in the table editor once loaded. This may also affect columns after this column, but I have not tested that.

How to repeat:
put "NULL ON UPDATE CURRENT_TIMESTAMP(6)" into any column's "Default/Expression"
[4 Jul 2017 7:11] MySQL Verification Team 
Hello Brian,

Thank you for the report.

Thanks,
Umesh
[4 Jun 2020 18:22] Christine Cole 
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.21 release, and here's the proposed changelog entry from the documentation team:

A column created with NULL ON UPDATE CURRENT_TIMESTAMP(6) prevented the
MySQL Table Editor from showing table information, such as indexes, views,
foreign keys, and so on.

Thank you for the bug report.