3 ms·
> Dealing with timezones will drive you mad, quickly. I guess you mean "implementing timezone logic yourself". other than that, the suggested approach (store
by pantulis 2y ago
> Dealing with timezones will drive you mad, quickly.
I guess you mean "implementing timezone logic yourself". other than that, the suggested approach (store everything in UTC) and translating to the relevant user timezone with a TZ database in the frontend is the way to go.
- plibblr 2y agoNot sure, that's good advice for times in the past, or for times in the next few months, but if we're arranging to meet at midday local time in two years time, I don't think a change in timezone rules in 2025 should cause our meeting to take place at a different time. I suppose you could store the meeting in UTC and use the creation time of the meeting to decide to use the 2024 timezone rules for conversion not the 2026 rules, but that seems pretty confusing too!