When copying my tables from a 4.1 server to a 4.0 server, I get charset errors. To get around this problem, I have to Export as SQL Dump, edit the dump file removing all charset references, and importing to the 4.0 server. *sigh*
Can SQLyog please be made to ignore the charset for databases that don't support charset?
Full Version: Mysql 4.1 To Mysql 4.0 Charset Problems
read here:
http://www.webyog.com/forums/index.php?sho...st=0&#entry6846
Simply delete the charset's definition from the SQL-file using Notepad or another editor.
it is not a SQLyog issue - it is a MySQL issue!
http://www.webyog.com/forums/index.php?sho...st=0&#entry6846
Simply delete the charset's definition from the SQL-file using Notepad or another editor.
QUOTE
Can SQLyog please be made to ignore the charset for databases that don't support charset?
it is not a SQLyog issue - it is a MySQL issue!
and BTW ...
the "workaround is there". You can use the ODBC-tool!
the "workaround is there". You can use the ODBC-tool!
QUOTE (peterlaursen @ Aug 14 2005, 03:49 PM)
Simply delete the charset's definition from the SQL-file using Notepad or another editor.
it is not a SQLyog issue - it is a MySQL issue!
it is not a SQLyog issue - it is a MySQL issue!
SQLyog uses MySQL's SHOW CREATE table statement in the generated dump file. The other option would be to read thru each and every columns definition and create the CREATE TABLE statement.
We prefer to use MySQL's SHOW CREATE table option because it is easier to keep up with the changes that MySQL does from version to version.
i cant access this page!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.