News for hackers. Stuff that matters.

A comment on Breaking our Latin-1 assumptions (2017). Parent comment

Re:Breaking our Latin-1 assumptions (2017) by iso1631 on Sunday June 19, 2022 @03:40AM (#31797127)
If I create a meeting for next November at 1600 local time in paris, and it's stored at 1500 UTC, what happens if France decides to stick with summer time between now and then. The meeting is still 1600 Paris, but the time will be 1400 UTC.

Similarly if I want a task to run at 6AM local time every day

If a time is in the future you usually want to store it as local time because we don't know what the offset between local and UTC will be.

[ Parent | on HN ]
Re:Breaking our Latin-1 assumptions (2017) by throwaway290 on Sunday June 19, 2022 @07:00AM (#31798196)
For some purposes concerning local future event scheduling you are right that it may be necessary to store date-time representation with timezone (or location, if it's possible to reliably infer timezone from location) and calendar (if non-Gregorian) rather than absolute UTC stamp. Not sure how common such cases are, compared with recording timestamps of past events.
[ Parent | on HN ]