[ENHANCEMENT] Enable specifying a project-specific timezone
srcds opened this issue · 5 comments
Testing the upcoming ARX version 3.9.1 revealed a bug in the date hierarchy wizard. For rather old dates (before 1900) the days are outputted with an offset of -1 day when creating hierarchies. Also, the dates (which were provided without hours and minutes) are associated with 23:53:28 when selecting the dd.MM.yyyy-HH:mm format in the wizard. Expected would be 00:00:00.
Example project:
arx_391_old_dates.zip
Not sure whether it really is a bug:
https://postgrespro.com/list/thread-id/1228096
What happens, when using a format without hours, minutes and seconds?
Quote: "I refer you to the IANA timezone database's entry for Europe/Berlin:
Zone NAME GMTOFF RULES FORMAT [UNTIL]
Zone Europe/Berlin 0:53:28 - LMT 1893 Apr 1:00 C-Eur CE%sT 1945 May 24 2:00 1:00
SovietZone CE%sT 1946 1:00 Germany CE%sT 1980 1:00 EU CE%sT
which says that timekeeping before April 1893 was done according to local mean solar time, 53:28 east of Greenwich; so a timestamp specified as midnight GMT+1 comes out as 23:53:28 local time."
What happens, when using a format without hours, minutes and seconds?
The offset also appears when just using Day/month/year. As shown in Level-4 on the screenshot above.
Ah, true.
OK. Took a look at this. It is not really a bug, just that the UI currently uses the local timezone. So this is actually a feature request:
(1) Enable specifying a per-project timezone as part of the protect properties
(2) Enable using project-specific or another user-specified timezone in the UI hierarchy builder.