Bug #60395 | show global variables requrns weired warnings on JP MS Windows. | ||
---|---|---|---|
Submitted: | 8 Mar 2011 17:40 | ||
Reporter: | Meiji KIMURA | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Windows | Severity: | S3 (Non-critical) |
Version: | 5.1.56, 5.5.9 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[8 Mar 2011 17:40]
Meiji KIMURA
[8 Jan 2014 7:18]
Sergei Kulakov
I confirm the bug on Windos 7. My Windows is Russian and so the system timezone is in Russian (Moscow time). It is returned by Windows and I can't change it (nor should I). The variable time_zone=SYSTEM hence MySql reads system_time_zone. Usually when I have to deal with Cyrillic strings I set variables character_set* to the right value (Set Names='cp1251') and that does the trick. But in this case even though I set all the variables except character_set_system to cp1251 the warning is still there. I have no control over that because MySql reads the value from the system, not from a table.
[4 Mar 2021 11:44]
MySQL Verification Team
The situation is same for MySQL 5.6/5.7/8.0 on Windows 10. mysql> show global variables like 'system_time_zone'; +------------------+-------+ | Variable_name | Value | +------------------+-------+ | system_time_zone | | +------------------+-------+ 1 row in set, 1 warning (0.01 sec) mysql> show warnings; +---------+------+--------------------------------------------------------------------------------------+ | Level | Code | Message | +---------+------+--------------------------------------------------------------------------------------+ | Warning | 1366 | Incorrect string value: '\x93\x8C\x8B\x9E (...' for column 'VARIABLE_VALUE' at row 1 | +---------+------+--------------------------------------------------------------------------------------+ 1 row in set (0.00 sec) mysql> select @@version; +-------------------+ | @@version | +-------------------+ | 8.0.22-commercial | +-------------------+ 1 row in set (0.00 sec)