Daylight saving time - do and don'ts

Posted by Oded on Stack Overflow See other posts from Stack Overflow or by Oded
Published on 2010-03-28T11:37:14Z Indexed on 2010/03/28 11:43 UTC
Read the original article Hit count: 478

I am hoping to make this question and the answers to it the definitive guide to dealing with daylight saving time, in particular for dealing with the actual change overs.

Many systems are dependent on keeping accurate time, the problem is with changes to time due to daylight savings - moving the clock forward or backwards.

For instance, one has business rules in an order taking system that depend on the time of the order - if the clock changes, the rules might not be as clear. How should the time of the order be persisted? There is of course an endless number of scenarios - this one is simply an illustrative one.

  • How have you dealt with the daylight saving issue?
  • What assumptions are part of your solution? (looking for context here)

As important, if not more so:

  • What did you try that did not work?
  • Why did it not work?

I would be interested in programming, OS, data persistence and other pertinent aspects of the issue.

General answers are great, but I would also like to see details especially if they are only available on one platform.

© Stack Overflow or respective owner

Related posts about system-design

Related posts about daylight-saving