SEO

This is a create table statement output from mysqldump from a 4.0.24
installation.

Restoring on 5.0.22 gives a warning.

Can anyone enlighten me?

I guess I'm a little behind on my reading...

David

mysql> CREATE TABLE `container` (
-> `carrier` varchar(128) NOT NULL default '',
-> `lock1` varchar(7) NOT NULL default '',
-> `lock2` varchar(7) NOT NULL default '',
-> `lock3` varchar(7) NOT NULL default '',
-> `lock4` varchar(7) NOT NULL default '',
-> `lock5` varchar(7) NOT NULL default '',
-> `lock6` varchar(7) NOT NULL default '',
-> `lock7` varchar(7) NOT NULL default '',
-> `lock8` varchar(7) NOT NULL default '',
-> `lock9` varchar(7) NOT NULL default '',
-> `lock10` varchar(7) NOT NULL default '',
-> `lock11` varchar(7) NOT NULL default '',
-> `lock12` varchar(7) NOT NULL default '',
-> `lock13` varchar(7) NOT NULL default '',
-> `lock14` varchar(7) NOT NULL default '',
-> `lock15` varchar(7) NOT NULL default '',
-> `lock16` varchar(7) NOT NULL default '',
-> `lock17` varchar(7) NOT NULL default '',
-> `lock18` varchar(7) NOT NULL default '',
-> `lock19` varchar(7) NOT NULL default '',
-> `lock20` varchar(7) NOT NULL default '',
-> `lock21` varchar(7) NOT NULL default '',
-> `lock22` varchar(7) NOT NULL default '',
-> `lock23` varchar(7) NOT NULL default '',
-> `lock24` varchar(7) NOT NULL default '',
-> PRIMARY KEY (`carrier`)
-> ) TYPE=MyISAM;
Query OK, 0 rows affected, 1 warning (0.00 sec)

Hi ,

dpgirago@mdanderson.org wrote:
> This is a create table statement output from mysqldump from a 4.0.24
> installation.
>
> Restoring on 5.0.22 gives a warning.
>
> Can anyone enlighten me?
>
> I guess I'm a little behind on my reading...
>
> David
>
> mysql> CREATE TABLE `container` (
> -> `carrier` varchar(128) NOT NULL default '',
> -> `lock1` varchar(7) NOT NULL default '',
> -> `lock2` varchar(7) NOT NULL default '',
> -> `lock3` varchar(7) NOT NULL default '',
> -> `lock4` varchar(7) NOT NULL default '',
> -> `lock5` varchar(7) NOT NULL default '',
> -> `lock6` varchar(7) NOT NULL default '',
> -> `lock7` varchar(7) NOT NULL default '',
> -> `lock8` varchar(7) NOT NULL default '',
> -> `lock9` varchar(7) NOT NULL default '',
> -> `lock10` varchar(7) NOT NULL default '',
> -> `lock11` varchar(7) NOT NULL default '',
> -> `lock12` varchar(7) NOT NULL default '',
> -> `lock13` varchar(7) NOT NULL default '',
> -> `lock14` varchar(7) NOT NULL default '',
> -> `lock15` varchar(7) NOT NULL default '',
> -> `lock16` varchar(7) NOT NULL default '',
> -> `lock17` varchar(7) NOT NULL default '',
> -> `lock18` varchar(7) NOT NULL default '',
> -> `lock19` varchar(7) NOT NULL default '',
> -> `lock20` varchar(7) NOT NULL default '',
> -> `lock21` varchar(7) NOT NULL default '',
> -> `lock22` varchar(7) NOT NULL default '',
> -> `lock23` varchar(7) NOT NULL default '',
> -> `lock24` varchar(7) NOT NULL default '',
> -> PRIMARY KEY (`carrier`)
> -> ) TYPE=MyISAM;
> Query OK, 0 rows affected, 1 warning (0.00 sec)

I would say the warning is caused by TYPE=MyISAM. TYPE= is deprecated in 5.x, and is
being replaced by ENGINE=. If you execute SHOW WARNINGS right after a statement that
generates warnings, you will see the warning text.

Cheers
Baron