Bug #66681 | Timezone support on Windows | ||
---|---|---|---|
Submitted: | 4 Sep 2012 12:31 | Modified: | 5 Sep 2012 20:16 |
Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Installing | Severity: | S3 (Non-critical) |
Version: | any | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[4 Sep 2012 12:31]
Peter Laursen
[5 Sep 2012 19:40]
Sveta Smirnova
Thank you for the report. This is not Windows issue. Look at the output from my Linux machine: mysql> SELECT @@global.time_zone, @@global.system_time_zone;+--------------------+---------------------------+ | @@global.time_zone | @@global.system_time_zone | +--------------------+---------------------------+ | SYSTEM | EEST | +--------------------+---------------------------+ 1 row in set (0.00 sec) mysql> select * from mysql.time_zone_name where name like '%EEST%'; Empty set (0.00 sec) This is issue of how OS timezones stored. Please also note select CONVERT_TZ(NOW(),'SYSTEM', 'US/Central'); perfectly works and returns correct results. So this can be either "Not a Bug" or documentation request.
[5 Sep 2012 20:16]
Sveta Smirnova
Reporter of bug #66678 complains, so I verified it as documentation bug and set this as duplicate: they are really about same thing.