Having Problems with database dump & importing with Mysql 4 to mysql 3.23

I’m having a lot of errors trying to read the dump from my database (mysql 4) in my localhost to a hosting server using mysql 3.23... I’ve read somewhere that removing the comments would solve the problem but, it didn’t... I’ve tried also the modbackup but I still have the errors... The strangest thing happens when I try to read the dump to another database in my localhost I still have errors

In mysql 3.23 after removing the comments The errors are like this:You have an error in your SQL syntax near ’ENGINE=MyISAM DEFAULT CHARSET=latin1’

Can anyone help me please??
Thanks

I had this problem too on my server >:(

Just remove all occurences of ENGINE=MyISAM DEFAULT CHARSET=latin1; of your SQL queries.

Another way is you replace ENGINE=MyISAM with TYPE=MyISAM and remove DEFAULT CHARSET=latin1;

Boby

Cadju, lots of us have been there

Boby is right, this is what makes the import fail.

You can also select (if your version of phpMyAdmin has the option) the MYSQL323 compatibility option when exporting. It will automatically strip your SQL of any incompatible statement.

:) Thanks people, now it works, but I’m having problems now with the characters like ç, è ú, etc , and another strange thing: the images from the content edited with the rich text editor doesn’t appear in the pages altough they appear in the preview in manager section when editing a page Any ideas??

Thanks in advance

When going back to 3.23, make sure you select latin1 as the file encoding when executing your sql dump in phpMyAdmin. If that still doesn’t work, you’re probably going to have to do some research to make sure you dump the data out properly, specify the character set and collation sequences of the db in 3.23 properly, and work through it.

Also keep in mind that the default encoding in these older versions of MySQL is actually cp1252, even though it is called latin1, and that most MySQL installs use latin1_swedish_ci as the default collation sequence.