Geek asks and answers

Poor MySQL import, now we have garbage instead of utf-8 chars

We restored the new MySQL structure from a backup in a different format (which is correctly configured to support UTF-8). We have strange characters displayed in the browser, but we are not sure what they are called, so we can find the main list of what they translated.

I noticed that they really correlate with a specific character. For instance:

â„¢ always translates to ™
â€" always translates to —
• always translates to ·

I referred to this post that started me, but this is far from a complete list. Either I'm not looking for the right name, or the "main list" of these "bad to good" conversions, because the link does not exist.

Reference: Error detection in utf8 in MySQL

Also, when I try to search for MySQL, if I search â, I always get MySQL, treating it as "a". Is there a way to tune my MySQL queries so that they become more literal searches? We do not use internationalization, so I can safely assume that any fields containing the â character are considered a problematic record that needs to be fixed using our "fixit" script, which we create.

+3
source share
1 answer

, "fixit" script , , . , , UTF-8, , , UTF-8, . , , , . , , , , , in. , , . :

http://www.istognosis.com/en/mysql/35-garbled-data-set-utf8-characters-to-mysql-

BINARY, . ( , , ). , UTF-8. , .

+2

More articles:


All Articles