Bug #58349 config wizard uses depreciated option
Submitted: 20 Nov 2010 20:18 Modified: 26 Mar 2013 5:56
Reporter: Peter Laursen (Basic Quality Contributor) Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Installing Severity:S3 (Non-critical)
Version:5.1.53, 5.5.7 OS:Windows
Assigned to: CPU Architecture:Any
Tags: qc

[20 Nov 2010 20:18] Peter Laursen
Description:
My Windows event log contains several instances of this: 

"'--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead. "

'Source' is listed as 'MySQL" (with no version indication)

How to repeat:
With config wizard bundled with .msi installer select utf8 as default charset when installing/configuring.

Suggested fix:
use '--character-set-server' and not '--default-character-set'
[24 Nov 2010 20:25] MySQL Verification Team
Thank you for the bug report. What is the option wrote in the respective my.ini file?. Thanks in advance.
[24 Nov 2010 20:35] Peter Laursen
It reads like:

default-character-set=utf8

.. in both the the configuration file of 5.1 and 5.5 instances (but I have to admit that the configuration file may not necessarily be created with the configuration wizard(s) bundled with latest version(s) as I sometimes skip the configuration wizard when using the .msi installer).
[24 Nov 2010 20:51] Peter Laursen
I checked: http://dev.mysql.com/doc/refman/5.5/en/mysql-command-options.html#option_mysql_default-cha...

It reads:

--default-character-set=charset_name 

Use charset_name as the default character set for the client and connection. 
A common issue that can occur when the operating system uses utf8 or another multi-byte character set is that output from the mysql client is formatted incorrectly, due to the fact that the MySQL client uses the latin1 character set by default. You can usually fix such issues by using this option to force the client to use the system character set instead.

It is not listed here that --default-character-set is deprecated - so I guess it is not.  But why does such error message then occur in my Event Viewer?

I tried to restart both 5.1.53 and 5.5.7.  It looks like 5.1.53 (and not 5.5.7) logs this (wwrong?) warning to the error log.  But I am not perfectly sure due to this bug: http://bugs.mysql.com/bug.php?id=58355.  

I now think that the bug is that the Event Viewer report/warning is wrong.

To reproduce please
1) install 5.1.53 as a service
2) start service
3) Inspect Event Viewer ('Windows logs .. Program' group) for the record reading:

 "'--default-character-set' is deprecated and will be removed in a future release. Please use '--character-set-server' instead.

For more information, see Help and Support Center at http://www.mysql.com."
[24 Nov 2010 20:53] Peter Laursen
Plz see the error message from Event Viewer here.

Attachment: seeithere.jpg (image/jpeg, text), 157.44 KiB.

[24 Nov 2010 21:25] Peter Laursen
I think starting MySQL 5.1.53 like this

mysqld --no-defaults --default-character-set=<any charset>

.. will be enough to get ther warning logged.

If 
1) --default-character-set is deprecated, the config wizard should not use it and docs should have the information.
2) --default-character-set is *not* deprecated the server should not write this warning to EventViewer/ErrorLog.

I would like to set category to "server .. logs" (accordingly to how I now understand) - but there is no such category.
[24 Jan 2011 19:23] Peter Laursen
Starting 5.1.54 from command line yields:

C:\mysql5154\bin>mysqld
110124 20:10:20 [Warning] '--skip-locking' is deprecated and will be removed in
a future release. Please use '--skip-external-locking' instead.

I used one to the 'templates' (my-medium.ini) as options file.  So maybe the basic problems origines with the template (it does use '--skip-locking')?

I am not able to understand that it takes so long to conclude here. Either

1) --skip-locking' *is* deprecated.  In that case the templates should be updated and the config wizard  not use it either.  + docs should state it

or 

2) --skip-locking' *is not* deprecated.  In that case the server should not log this error.
[21 May 2011 19:13] Valeriy Kravchuk
All my.ini file "templates" we distribute should be updated to NOT include deprecated options.
[26 Mar 2013 5:56] Erlend Dahl
[20 Mar 2013 12:37] Reggie Burnett

The msi/config wizard combo has been replaced with the new MySQL Installer.
Please download a more recent server bundle and use the new MySQL Installer.