Better handling of locales #4

New issue

Open

opened 2022-08-21 13:09:09 +00:00 by snorremd · 0 comments

snorremd commented

2022-08-21 13:09:09 +00:00

(Migrated from github.com)

Tracks are registered with correct UTC time, there is however nothing indicating which timezone the user tracked time in. When computing the calendar a user might experience that a tracked time is placed on the wrong date as Postgres will use the UTC time when calculating which date to place the tracked time in.

To solve this the tracked time (and potentially targets) can include a new table column timezone that keeps track of which timezone time was tracked for. When getting the date of a track we can then get the start date with the correct time zone instead plain UTC.

`Tracks` are registered with correct UTC time, there is however nothing indicating which timezone the user tracked time in. When computing the calendar a user might experience that a tracked time is placed on the wrong date as Postgres will use the UTC time when calculating which date to place the tracked time in. To solve this the tracked time (and potentially targets) can include a new table column `timezone` that keeps track of which timezone time was tracked for. When getting the date of a `track` we can then get the start date with the correct time zone instead plain UTC.