Bug #22648 LC_TIME_NAMES: Setting GLOBAL has no effect
Submitted: 24 Sep 2006 19:51 Modified: 24 Apr 2007 16:57
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.12-beta-debug OS:Linux (SUSE 10.0 / 64-bit)
Assigned to: Alexander Barkov CPU Architecture:Any

[24 Sep 2006 19:51] Peter Gulutzan
Description:
When I set a GLOBAL variable, I expect that the setting
will take effect on other (new) connections. But with
LC_TIME_NAMES, there is no effect.

How to repeat:
On one connection, say:

SET GLOBAL LC_TIME_NAMES = 'ja_JP';

On another connection, started after the SET statement, say:

SELECT @@lc_time_names;
SELECT @@global.lc_time_names;
SELECT DAYNAME(CURRENT_DATE);
[24 Sep 2006 23:57] Godofredo Miguel Solorzano
Thank you for the bug report. Verified as described.
[22 Nov 2006 8:56] Alexander Barkov
mysqld should also support setting the global variable from
command line option at start up. Now it produces an error:

$./mysqld --lc_time_names=en_US
061122 12:48:38 [ERROR] ./mysqld: unknown variable 'lc_time_names=en_US'
[6 Apr 2007 10:12] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/23972
[9 Apr 2007 13:02] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/24051
[9 Apr 2007 13:07] Alexander Barkov
Commited again, with a better command line help message.
Pushed into 5.0.40-rpl.
[9 Apr 2007 13:30] Alexander Barkov
Pushed into 5.1.18-rpl
[20 Apr 2007 17:15] Bugs System
Pushed into 5.0.42
[20 Apr 2007 17:16] Bugs System
Pushed into 5.1.18-beta
[24 Apr 2007 16:57] Paul Dubois
Noted in 5.0.42, 5.1.18 changelogs.

Using SET GLOBAL to change the lc_time_names system variable had no
effect on new connections.