[rgf101]

Excellent, the new build works. Many thanks.

[rgf101]

'peterlaursen' wrote on '23:

Could you please attach a small dump? It can be a single table with a few rows with silly data only as long as it is reproducible.

Sure.

I've now tested with both Wampserver and Easyphp, as I suspected Wampserver might have been doing something odd. However, still no joy. Everything works perfectly except that stage of importing the mysql dump. Everything I can see is set to utf8 – if there's something specific I should check, do let me know though, as I'm no expert.

The attached dump has table structure data and three rows. The second of these rows should contain a short Chinese phrase, '活着就好'. I can open it fine in notepad, so the info is in there.

Many thanks for your help, especially considering the time of year – encoding issues aren't very Christmassy.

[rgf101]

Have actually already tried that after some more investigating, but it hasn't helped. I'm really pretty mystified, I can see no more references to anything other than utf8 (

Code:

character_set_client utf8
character_set_connection utf8
character_set_database utf8
character_set_results utf8
character_set_server utf8
character_set_system utf8
collation_connection utf8_general_ci
collation_database utf8_general_ci
collation_server utf8_general_ci

), the settings for the database, table and columns are all as they should be, and yet it's still failing to import a utf8 dump correctly. I'm either missing something incredibly obvious, or there's something odd happening somewhere (quite possibly not within SQLyog, it could equally be Wampserver / MySQL itself at this point.)

Any other ideas gratefully listened to . . .

[rgf101]

I'm creating the dumps with phpMyadmin, so basically I can only take what it gives me. I can upload a sample file if you want, but I don't think it's going to help – seems we know what the problem is.

Quote:

server default is not utf8.

Which specific variable is this? I can add that to my.ini, and presumably that should fix the issue?

Quote:

However it would be no technical difficulty to add an option for user to specify query(ies) that could be executed in the import thread before executing the file. Is that what you request?

That I suppose would be one solution, or allow us to SET NAMES for the connection that reads sql files? I'm not sure, that's probably a decision for you. But adding it into the top of every dump file is pretty inefficient and with very large dump files pretty much impossible.

I don't mind changing config files if necessary, so if you can let me know what changes I need to make I'll give it a shot. Thanks for you help.

[Author]

Posts