mysqldump 5.0.22 -> 4.1.20

[thedaver]

I have a large database (both linux) on mysql 5.0.22 where tables don't use any particularly exotic features and their table type is:
ENGINE=MyISAM DEFAULT CHARSET=latin1;

I have a need to copy these tables to a 4.1.20 server.

Before I run a rather lengthy/long mysqldump to get the table contructs and row data exported, I'd like to hear from the list (PLEASE!) whether there are any gotchas out there.

I created the database using a script that dates back to mysql v3.xx.xx, so I don't believe there are many risks, but if 'mysqldump' on v 5.0.22 has any compatibility options, I certainly don't see them.

Thanks!

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/

 

[TonyGroves]

The only problem there might be is if your tables contain any recently-introduced data types or features. If they date back to v.3.23, they should be OK, since the dumpfiles just contain the SQL code needed to recreate them.

 

[thedaver]

Thanks Tony;
I presumed as much and have done most of the processing.
So far the structures took... applying the rows now.
No errors, so looks like it'll be ok.
Thanks!

D.E.R. Management - IT Project Management Consulting

http://www.dermanagement.com/