how do you deal with timezone issues? [duplicate]

Question

This question already has an answer here:

How to store repeating dates keeping in mind Daylight Savings Time (1 answer)

Closed 2 years ago.

For a scheduling system, what's the best way to save the timezone of client/event in a central server database coming from multiple sources mobile,web,client app.

• How do you store the dates? Alarms, reminders etc...
• How do you handle the DST setting?
• How do you handle the events if client has traveled to a different location?

I need the solution to work with all databases in tags.

Answer 1

Store dates as UTC timestamps - convert to local time when displaying data to the user.

Answer 2

Everything in UTC, and another column for the offset.

Answer 3

These are the key points to the strategy I tend to use.

• Every date is UTC internally to the system.
• Users are shown dates in the their local timezone.
• We allow users to override the timezone they are using in case they travel and they want to keep the timezone consistent.
• Make the timezone easily visible. Either display it with the time or as part of the column header.

Answer 4

1. Safe to store in one specific time zone ideally in UTC
2. If you store the time with a date, you are safe in DST.
3. Suggesting you to use a web service to find the time difference.