Re:Don't Do This with PostgreSQL
by codr7 on Tuesday November 12, 2024 @01:08PM
(#42118000)
Enforcing UTC inside the system and converting to the correct time zone for display purposes is fine though. Makes a lot of sense when the recorded time zone isn't relevant in itself, booking systems for example.
[ Parent
| on HN ]
Use UTC + convert to local time for display if the time is a global event, i.e. something that happens at the same time everywhere. E.g. an online meeting, conference start time, missile launch schedule, etc.
Use time + timezone if the time is always local to a particular user and should follow their time zone. E.g. wake up alarm, eat breakfast schedule,
The problem is these definitions are already a bit fuzzy and it's not always clear which type it is even to the person creating it.