3 ms·
UTC for data is perfect for events that have occurred. It has corner cases for planned future timing that require further thought and probably storing wall time
by wwweston 1y ago
UTC for data is perfect for events that have occurred. It has corner cases for planned future timing that require further thought and probably storing wall time + locale.
- Eddy_Viscosity2 1y agoI can see that would be an issue. Fortunately I guess, I don't have to deal with future events (except in case where the date formatting is ambiguous and I guess wrong, resulting in events appearing to have occurred in the future).