5 ms·
The most common situation I know of where you store the time with its original TZ is when dealing with recurring times (opening/closing items, appointments), as
by unilynx 6y ago
The most common situation I know of where you store the time with its original TZ is when dealing with recurring times (opening/closing items, appointments), as you need to follow the original DST/summertime the user was in.
Which also requires you to store the TZ location (ie city) and not just the name or offset of the timezone itself.
- AmericanChopper 6y agoYeah, I meant to put a “usually” qualifier in that previous comment. Rostering has the same problem. Event scheduling can also run into similar problems. The best solution really depends on a lot of context specific details, but most of the better solutions I’ve personally seen have put TZ in a seperate field, rather than using TZ-typed timestamps, and then use the TZ when required instead of as the default storage format.