MySQL Bugs: #70036: character-set-client option ignored in my.cnf

Bug #70036	character-set-client option ignored in my.cnf
Submitted:	14 Aug 2013 17:22	Modified:	6 Jun 2014 13:28
Reporter:	Franjo Markovic	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Options	Severity:	S3 (Non-critical)
Version:	5.6.13	OS:	MacOS (10.6)
Assigned to:		CPU Architecture:	Any

Description:
I have added a following line in my.cnf:

character-set-client=utf8mb4

and after restarting the server I got the warning in the .err file:

2013-08-13 20:44:29 0 [Warning] Using unique option prefix character-set-client instead of character-set-client-handshake is deprecated and will be removed in a future release. Please use the full name instead.

2013-08-13 20:44:29 0 [Warning] /usr/local/mysql/bin/mysqld: ignoring option '--character-set-client-handshake' due to invalid value 'utf8mb4'

How to repeat:
add in my.cnf:

character-set-client=utf8mb4

Suggested fix:
Per online documentation, "character-set-client" is a valid variable, while "character-set-client-handshake" is not. The same line/settings in my.ini on windows worked fine.

Funny coincidence.
A few days ago I reported http://bugs.mysql.com/bug.php?id=69997

(skip-character-set-client-handshake is not a variable, but it is an option. Do you start the server with this option?)

Well, I see a bunch of inconsistencies here. Why would some options at all be available only from command line, some only as my.cnf options, and some only as system variables ?! It should just all be available either way.

Thank you for the bug report.