5 ms·
No, its not a silver bullet but it almost is. For a vast majority of use cases, UTC storage is sufficient. For everything else, you need both the UTC timestamp
by bob1029 5y ago
No, its not a silver bullet but it almost is.
For a vast majority of use cases, UTC storage is sufficient. For everything else, you need both the UTC timestamp and some other piece of knowledge depending on the scenario at hand. In many cases, its as simple as a User.UtcOffsetMinutes fact. In other more paranoid scenarios, you may be inclined to store the original timezone/offset in which the UTC fact was originally valid.
Regardless of the scenario, there is no situation where I would want to store a non-UTC timestamp. Everything is UTC with some optional extras.