MySQL Bugs: #41152: Primary Key of INT(N) in Catalog Edit Table is incorrectly displayed as INTEGER

Bug #41152	Primary Key of INT(N) in Catalog Edit Table is incorrectly displayed as INTEGER
Submitted:	1 Dec 2008 14:57	Modified:	11 Feb 2009 13:30
Reporter:	Lucas Redding	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Administrator	Severity:	S3 (Non-critical)
Version:	1.2.12	OS:	Windows (W2003 SP2)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	W2003 Server + SP2

Description:
I have a table called 'class' that has been defined as follows:

CREATE TABLE `class` (
  `ID` int(10) unsigned NOT NULL auto_increment,
  `Name` varchar(128) NOT NULL,
  `Type` enum('REQ','ARCH','DESIGN') NOT NULL,
  `Model_Class_ID` varchar(64) NOT NULL,
  PRIMARY KEY  (`ID`)
) ENGINE=InnoDB  DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

However when editing the table in 
"MySQL_Administrator/Catalog/<SCHEMA>/Edit_Table"

When selecting column 'ID' the information is displayed for that column as follows:

Name: ID
Data type: INTEGER
Column Options: Primary Key, Not NULL, Auto increment
Flags: UNSIGNED

Clearly the "Data type" property should be INT(10) and not INTEGER.

I have several similar tables and the problem is consistent in all the tables. Interestingly any columns that are not primary keys and are of INT(N) are displayed correctly.

How to repeat:

Create the following table in SQL command line:

CREATE TABLE `class` (
  `ID` int(10) unsigned NOT NULL auto_increment,
  `Name` varchar(128) NOT NULL,
  `Type` enum('REQ','ARCH','DESIGN') NOT NULL,
  `Model_Class_ID` varchar(64) NOT NULL,
  PRIMARY KEY  (`ID`)
) ENGINE=InnoDB  DEFAULT CHARSET=latin1 AUTO_INCREMENT=2 ;

Launch MySQL administrator/Catalog/<SCHEMA>/Edit_Table and select Column 'ID'.

It will be displayed as INTEGER and not INT(10).

Thank you for the bug report.

Sorry. 

I meant to say that I have only witnessed this in Windows Server 2003.

Regards

Lucas Redding

Fixed in repository common, revision 718