Today, when logging into the database server, the following error occurred:
1 [[email protected] app]# mysql-uroot-p2'Character-set-client=utf8 '
Check the next my.cnf configuration file, is in the client section under the configuration of such an option, according to the truth, there will be no problem ah, then the internet Google Down, found:
Understand that this is a bug in Mysqlbinlog. Since client-side encoding is allowed through the Character_set_client option in the Client option group, why does the tool that comes with mysqlbinlog not recognize this option?
Even if you do not know here, it does not have to go directly to the error and quit running, if you do not know this option only to skip this option (you can give a notice hint that you do not know this option is better) continue to run better?
But one problem is that I have no problem using Character-set-server = UTF8 under the mysqld section.
Therefore, my solution is: to comment the above Character_set_client=utf8, and then restart, so that when logging in, only the client side of the encoding is not UTF8, so we are in the
With set global Character_set_client=utf8, the entire database is encoded in UTF8.
1 Server characterset: UTF82Db characterset: UTF83Client CharacterSet: UTF84 Conn. CharacterSet: UTF8
Unknown variable ' Character_set_client=utf8 ' error occurred while logging in to MySQL