| Bug #87907 | MySQL Workbench: Autocompleting suggests TIMESTAMP incorrectly | ||
|---|---|---|---|
| Submitted: | 29 Sep 2017 7:11 | Modified: | 21 Mar 2018 16:02 |
| Reporter: | Ted van Riel | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | 6.3.9 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | autocomplete, workbench | ||
[29 Sep 2017 8:39]
MySQL Verification Team
Hello Ted van Riel, Thank you for the report and feedback. Thanks, Umesh
[21 Mar 2018 14:49]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 8.0.11 release, and here's the changelog entry: Code completion did not provide a suggestion for the SELECT statement or for system variables. In addition, types like TIMESTAMP were completed with the wrong type values. Thank you for the bug report.
[21 Mar 2018 16:02]
Ted van Riel
Thank you very much guys! Have a nice day.
Description: Workbench suggests the TIMESTAMP type incorrectly. How to repeat: - Create a new column in a new table, - set the type to "TIMEST" and observe how auto-complete suggests "TIMESTAMP()", - select the suggestion, filrling in TIMESTAMP() as a type - jump to the next column and observe how the type gets reverted to the previous value as TIMESTAMP() is not a correct datatype. Suggested fix: Change the autocomplete suggestion to the correct "TIMESTAMP"