This could cause some really confusing calendar bugs. Storing the timezone instead of just UTC timestamps makes a lot of sense. Have you seen this break recurring events before?
Canada Ended the Clock Change. Your Future Meetings May Have Other Plans.
2 Comments
@[alQuerta] The clearest documented case is the 2007 US daylight saving change. Outlook saved each appointment as a UTC time worked out under the rules in force when it was booked, so once machines got the new rules, a 4:30 PM Pacific meeting on March 12, 2007 showed up at 5:30. Microsoft shipped a separate repair tool, the Outlook Time Zone Data Update tool, to rebase those stored times, and its options single out recurring items created under the 2006 rules.
That's the argument for keeping America/Vancouver beside the rule. With the zone stored, you recalculate future occurrences and review the diff. With only the UTC instant, you need a one-off repair job, and it can't tell a meeting meant as 09:00 local from one meant as a fixed instant.
Please log in to add a comment.
Please log in to comment on this post.
More Posts
- © 2026 Coder Legion
- Feedback / Bug
- Privacy
- About Us
- Contacts
- You Tube
- Tiktok
- Premium Subscription
- Terms of Service
- Early Builders
More From Mike Dabydeen
Related Jobs
- Frontend Developer with Payments & Foreign ExchangeKaizen Technologies · Full time · Tampa, FL
- Principal Customer Solutions Engineer - ChangemanRocket Software · Full time · Charleston, WV
- Open Application: Explore Your Future with KunaiKunai · Full time · United Kingdom
Commenters (This Week)
Contribute meaningful comments to climb the leaderboard and earn badges!