MySQL Forums
Forum List  »  General

No big deal, but...
Posted by: Eric Blankfield
Date: February 16, 2005 04:21PM

Anyone know why this may have happened. I couldn't really care less which datatype 'move' is, but I am interested as to why MySQL did this...

mysql> desc dcr;
+--------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------+------------------+------+-----+---------+----------------+
| id | int(10) unsigned | | PRI | NULL | auto_increment |
...
| move | char(2) | YES | | NULL | |
...
+--------------+------------------+------+-----+---------+----------------+
22 rows in set (0.00 sec)

mysql> alter table dcr change move move char(5);
Query OK, 5669 rows affected (1.14 sec)
Records: 5669 Duplicates: 0 Warnings: 0

mysql> desc dcr;
+--------------+------------------+------+-----+---------+----------------+
| Field | Type | Null | Key | Default | Extra |
+--------------+------------------+------+-----+---------+----------------+
| id | int(10) unsigned | | PRI | NULL | auto_increment |
...
| move | varchar(5) | YES | | NULL | |
...
+--------------+------------------+------+-----+---------+----------------+
22 rows in set (0.00 sec)

Options: ReplyQuote


Subject
Written By
Posted
No big deal, but...
February 16, 2005 04:21PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.