Bug #72365 Column data type is not retrieved, unable to alter tables
Submitted: 17 Apr 2014 10:38 Modified: 29 Oct 2014 13:17
Reporter: Onur Şafak Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.1.4.11773 build 1454 community ed OS:Microsoft Windows (8.1 Pro)
Assigned to: CPU Architecture:Any
Tags: datatypes

[17 Apr 2014 10:38] Onur Şafak
Description:
In table editor and diagram designer, column data types other than 'VARCHAR' are not shown.

In table editor, 'datatype' column only shows the precision / length for these columns, like: (10). Trying to save the table results with a datatype error.

- No problem with 3rd party software
- Server: 5.6.17 Windows 64 bit Community Ed. same results with 5.5

WORKAROUND:

Open the table in inspector and re-set the column data types in the editor one by one before saving.

NO Workaround is available for the diagram interface.

How to repeat:
- right click on schemas/information_schema/tables/CHARACTER_SETS, click Alter Table

- See MAXLEN column data type is listed as: (3)

ALSO

- create a new table with various types of columns, see the datatypes immediately become like '(10), (3)' when you save the table.
[17 Apr 2014 10:39] Onur Şafak
mysql workbench datatype trouble

Attachment: mysql-workbench-datatype-trouble.jpg (image/jpeg, text), 39.86 KiB.

[25 Apr 2014 18:39] Alfredo Kojima
Are you using a turkish locale?
[28 Apr 2014 9:19] Onur Şafak
The system locale is Turkish. For databases and tables utf8_unicode_ci, utf8_turkish_ci, latin5 collations are used.
[28 Apr 2014 10:53] Onur Şafak
Just tested. It's not the system locale but the date & number formats in the region dialog. Once set to English, everything looks normal.
[29 Sep 2014 13:17] MySQL Verification Team
Please try version 6.2.3 version. Thanks.
[30 Oct 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".