About arrow Support Forums Make Text BiggerMake Text SmallerReset Text Size
Export Content Support
Welcome, Guest
Please Login or Register.    Lost Password?
utf8 data migration between J1.0 and J1.5 issue (1 viewing) (1) Guest
Go to bottom Post Reply Favoured: 0
TOPIC: utf8 data migration between J1.0 and J1.5 issue
#1327
skyfranky (User)
Fresh Boarder
Posts: 9
graphgraph
User Offline Click here to see the profile of this user
utf8 data migration between J1.0 and J1.5 issue 4 Months, 1 Week ago Karma: 0  
Hi, Steve

I have successfully migrated my J1.0 uft8 data to J1.5 with export content. However, I have some problem to migrate my other custom tables to J1.5 using phpmyadmin and mysqldump, and I hope you can give me some hints since your export content works for the same DB, but just different tables.

I tried to export the tables using phpmyadmin and mysqldump, but the exported sql file that generated by both phpmyadmin and mysqldump can not show my utf8 chinese chars correctly.

I guess this issue is caused by J1.0 does not handle utf8 data saving correctly even DB is set to UTF8 already. J1.5 has no such problem.

Really appreciate if you can give me some ideas to fix this issue.
 
Report to moderator   Logged Logged  
 
Last Edit: 2008/07/28 14:50 By skyfranky.
  The administrator has disabled public write access.
#1328
Steve (Admin)
Admin
Posts: 207
graph
User Offline Click here to see the profile of this user
Re:utf8 data migration between J1.0 and J1.5 issue 4 Months ago Karma: 3  
Hi Franky,

QUOTE:
I tried to export the tables using phpmyadmin and mysqldump, but the exported sql file that generated by both phpmyadmin and mysqldump can not show my utf8 chinese chars correctly.


Do you mean they are garbled?
If so try BabelPad to view the dump locally, set the font to an Unicode font to see if it renders as it should:

If it looks ok try to import using "phpmyadmin" just copy/paste into the SQL window.
If the tables are already there you will only need to insert the "INSERT" statements from each table this may also help get around any "DEFAULT CHARSET" that has been incorrectly set in the source site.

It may also be a good idea first using "phpmyadmin" to use the empty feature to "TRUNCATE" the tables in question.
 
Report to moderator   Logged Logged  
 
Regards Steve.
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop