Bug #14566 convert INTEGER to INT(11) by mistake

• Submitted: 2 Nov 2005 9:48
• Modified: 3 Nov 2005 7:44
• Reporter: Hu Hailin
• Status: Not a Bug
• Category: MySQL Query Browser
• Severity: S3 (Non-critical)
• Version: 1.1.17
• OS: Windows (Windows XP Pro SP2)
• CPU Architecture: Any

[2 Nov 2005 9:48] Hu Hailin

Description:
When I create a table in MySQL Query Browser with a SQL sentence, it automatically convert the 'INTEGER' to 'INT(11)'. Maybe it won't hurt anyone, but 'INT(11)' is hardly meaningful.
However, if you create a table in other cases such as CMD or MySQL Administrator, the result is generally 'INT(10)'. So this is a bug, I guess.

How to repeat:
Write and execute the sql sentence below in the query area of Query Toolbar, check the type of 'id'.
create table test ( id integer );
desc test;

[3 Nov 2005 7:44] Valeriy Kravchuk

It is not a mistake, but consistent inteded behaviour. Look:

C:\Documents and Settings\openxs>mysql -uroot -p -P3307
Enter password: ****
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 3 to server version: 5.0.15-nt

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> use test;
Database changed
mysql> create table ttt (id integer);
Query OK, 0 rows affected (0.25 sec)

mysql> desc ttt;
+-------+---------+------+-----+---------+-------+
| Field | Type    | Null | Key | Default | Extra |
+-------+---------+------+-----+---------+-------+
| id    | int(11) | YES  |     | NULL    |       |
+-------+---------+------+-----+---------+-------+
1 row in set (0.09 sec)

So, mysql command line client works similarly.