RE: Backup problem from 5.0 to mysql 4.1
From: Amir Bukhari Sent: 18 July 2006 09:23 I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. Moving binary files between versions is generally a bad idea, use mysqldump instead. It creates a sql file you can run against the 4.1 server and should move all the chars over ok. E.g. if your database was called foodb then locally run: $ mysqldump -u amir -p foodb foodb.sql Then load this file into the server: $ mysql --host=server.name -u amir -p foodb foodb.sql (Or you could copy the dump file up to the server and then run the commmand locally.) Note the above will create all the tables and overwrite any existing tables and data with the new set. http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html mark -- MARK ADDISON WEB DEVELOPER 200 GRAY'S INN ROAD LONDON WC1X 8XZ UNITED KINGDOM T +44 (0)20 7430 4678 F E [EMAIL PROTECTED] WWW.ITN.CO.UK Please Note: Any views or opinions are solely those of the author and do not necessarily represent those of Independent Television News Limited unless specifically stated. This email and any files attached are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify [EMAIL PROTECTED] Please note that to ensure regulatory compliance and for the protection of our clients and business, we may monitor and read messages sent to and from our systems. Thank You. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: Backup problem from 5.0 to mysql 4.1
-Original Message- From: Addison, Mark [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 1:22 PM To: Amir Bukhari; mysql@lists.mysql.com Subject: RE: Backup problem from 5.0 to mysql 4.1 From: Amir Bukhari Sent: 18 July 2006 09:23 I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. Moving binary files between versions is generally a bad idea, use mysqldump instead. It creates a sql file you can run against the 4.1 server and should move all the chars over ok. E.g. if your database was called foodb then locally run: $ mysqldump -u amir -p foodb foodb.sql Then load this file into the server: $ mysql --host=server.name -u amir -p foodb foodb.sql I have tried this also, but this produce those bad character. I have used exactly what you have done above. When restoring the database which was backuped using mysqldump into mysql 5.0 everything is OK, but when restoring it to mysql 4.1 then there is those bad characters. I have also tried to backup and restore with both version of mysql mysqldump included in 5.0 and 4.1, but without success. -Amir -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Backup problem from 5.0 to mysql 4.1
Amir Bukhari wrote: -Original Message- From: Addison, Mark [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 18, 2006 1:22 PM To: Amir Bukhari; mysql@lists.mysql.com Subject: RE: Backup problem from 5.0 to mysql 4.1 From: Amir Bukhari Sent: 18 July 2006 09:23 I have local mysql 5.0 and I have developed an arabic site. The database encoding is utf8-bin. Localy everything work fine, all arabic text are displayed OK. Now I want to move it to a server in internet. The server has mysql 4.1 and as I restored the database there, some special arabic character are not displayed correctly. I don't know why only some character are inserted differently from others. Localy I have also tried to have both mysql server 4.1 5.0 to play with the backup and store, but without success, always the same result. Moving the binary database files (*.frm ...) from 5.0 to 4.1 doesn't work, it seem they are not compatible. Moving binary files between versions is generally a bad idea, use mysqldump instead. It creates a sql file you can run against the 4.1 server and should move all the chars over ok. E.g. if your database was called foodb then locally run: $ mysqldump -u amir -p foodb foodb.sql Then load this file into the server: $ mysql --host=server.name -u amir -p foodb foodb.sql I have tried this also, but this produce those bad character. I have used exactly what you have done above. When restoring the database which was backuped using mysqldump into mysql 5.0 everything is OK, but when restoring it to mysql 4.1 then there is those bad characters. I have also tried to backup and restore with both version of mysql mysqldump included in 5.0 and 4.1, but without success. There is a special commandline option for the mysqldump included in 5.0 to produce dumps suitable for 4.1. Try that. Bye Racke -- LinuXia Systems = http://www.linuxia.de/ Expert Interchange Consulting and System Administration ICDEVGROUP = http://www.icdevgroup.org/ Interchange Development Team -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]