Description:
See bug#8171.
A problem exists with the "true varchar" change:
if I create a table with a VARCHAR column in 5.0.3,
then try to read the database with a 4.1.x version
of MySQL (e.g. 4.1.10), I get an error:
ERROR 1033 (HY000): Incorrect information in file: '<table name>'
The message is too ambiguous. It should say:
Table '<table name>' was created with a different version of MySQL and cannot be read
How to repeat:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.3-alpha-debug
mysql> use tp;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> create table t1 (col1 int, col2 varchar(7500));
Query OK, 0 rows affected (0.01 sec)
mysql> show create table t1;
+-------+-----------------------------------------------------------------------
--------------------------------------------------------+
| Table | Create Table
|
+-------+-----------------------------------------------------------------------
--------------------------------------------------------+
| t1 | CREATE TABLE `t1` (
`col1` int(11) default NULL,
`col2` varchar(7500) default NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1 |
+-------+-----------------------------------------------------------------------
--------------------------------------------------------+
1 row in set (0.00 sec)
mysql> insert into t1 values (50,'hello');
Query OK, 1 row affected (0.01 sec)
mysql> quit;
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 4.1.10-debug
mysql> use tp;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Didn't find any fields in table 't1'
Database changed
mysql> select * from t1;
ERROR 1033 (HY000): Incorrect information in file: './tp/t1.frm'
