[MDEV-19243] Fix timezone handling on Windows to report POSIX timezone names Created: 2019-04-12  Updated: 2022-10-11  Resolved: 2019-04-30

Status: Closed
Project: MariaDB Server
Component/s: Server
Affects Version/s: 5.5, 10.0, 10.1, 10.2, 10.3, 10.4
Fix Version/s: 10.2.24, 10.1.39, 10.3.15, 10.4.5

Type: Bug Priority: Major
Reporter: Vladislav Vaintroub Assignee: Vladislav Vaintroub
Resolution: Fixed Votes: 0
Labels: Connectors, Windows

Issue Links:
Problem/Incident
causes CONJS-62 Support named timezones and daylight ... Closed
causes MDEV-29102 system_time_zone is incorrect on Wind... Closed
Relates
relates to MDEV-18948 Package time zone tables for Windows ... Open

 Description   

For JDBC/Node.js drivers at least, it is necessary to handle timezone information (system_time_zone, @session.time_zone) in the way that is independent from the underlying OS, and also POSIX locale names have to be supported. Currently, POSIX locale names are not accepted, and the server would report a rather unusable "Coordinated Universal Time".

The task is to make Windows behave like the other OSes do wrt to timezone information.
The mapping between Windows timezone names and POSIX is given by the "golden standard"

CLDR data https://unicode.org/repos/cldr/trunk/common/supplemental/windowsZones.xml

We can parse that to create map the names. It is also possible to find the DST setting and UTC offsets using Windows APIs GetTimezoneInformation etc.



 Comments   
Comment by Geoff Montee (Inactive) [ 2019-04-25 ]

MDEV-18948 might be related to this.

Comment by Vladislav Vaintroub [ 2019-04-30 ]

I fixed only system_time_zone. We're currently discussing how to package checking generated timezone related tables for any platform.

Generated at Thu Feb 08 08:50:08 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.