Answer the question
In order to leave comments, you need to log in
Error in encoding Russian characters when creating a database dump (hard mode)?
Briefly:
There is its own VDSka, when viewing the database on the server, Russian characters are displayed normally, when creating a dump, they are encoded in this form "Звонок ћП" when uploading to a new VDSka, everything is also readable. When outputting through php on the site, there are also Russian characters, BUT! Recently, they began to transfer the project to the local host, and when loading such a crooked dump into mysql openserver, the bugs were recorded as bugs and they are also displayed on the site.
More details:
Take for example the query SELECT cName FROM clients WHERE client_id = 65 - displays "Mikhail" In the dump, it will be written as "Миха
иÐ
"
on other krakozyabry or question marks.
mysql raised the standard of the standard repositories, the default settings:
character_set_client latin1 the
character_set_connection latin1 the
character_set_database the utf8
character_set_filesystem binary
character_set_results latin1 the
character_set_server latin1
character_set_system the utf8
character_sets_dir / usr / this content share / mysql / charsets /
collation_connection latin1_swedish_ci
collation_database utf8_unicode_ci
collation_server latin1_swedish_ci
database and a table set up with a standard for database encoding .
The exported file is defined with UTF-8 encoding by default
Krakozyabr encoding is determined by the autodecoder either as ISO-8859-1 or as Windows-1252, there are several more options.
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question