Bug #44552 INTEGER(n) not allowed, but INT(n) is ok
Submitted: 29 Apr 2009 18:09 Modified: 10 Jun 2009 13:52
Reporter: Karsten Wutzke Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.1.10 OS:Any
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: display width, INT, INTEGER, LENGTH

[29 Apr 2009 18:09] Karsten Wutzke 
Description:
When changing colum types to INTEGER(n) this is not allowed (rejected), but INT(n) gets accepted.

How to repeat:
Try to change a column's type to INTEGER(2) or similar and it will change back.

Suggested fix:
Same behavior as for INT(n) I suppose.
[29 Apr 2009 18:26] MySQL Verification Team 
Thank you for the bug report.
[30 Apr 2009 14:07] Karsten Wutzke 
This seems to be associated with

http://bugs.mysql.com/bug.php?id=41934
[3 Jun 2009 19:27] Johannes Taxacher 
fixed. will be included in 5.1.13
[10 Jun 2009 13:52] Tony Bedford 
An entry was added to the 5.1.13 changelog:

When in the Columns tab of the Table Editor, if an attempt was made to change a column data type to INTEGER(n) this would have no effect and the column data type would remain unchanged. However, if INT(n) was entered this was accepted and the data type changed accordingly.