Re: Error trying to migrate from 3.23.51 to 5.1.66
Solved:
The 3.23 mysqldump was inserting some comment lines that 5.1.66 didn't like.
I spent an hour in a memory friendly text editor (joe -- I like the WordStar keybindings) removing ALL comment lines from the 2GB "final" .sql file (after converting to UTF-8 and using sed to ensure autoupdates were clean).
The resulting file imported fine and the application using the database is happy with the result.
Thanks to a hint on freenode #mysql
Gerald
Subject
Views
Written By
Posted
6590
February 15, 2013 06:29PM
Re: Error trying to migrate from 3.23.51 to 5.1.66
2110
February 15, 2013 10:56PM
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.