4 ms·
You don’t need to store timestamps “in UTC”. You just need to store the time zone offset. That extra few bytes of precision representing where the timestamp sen
by jimmytucson 5y ago
You don’t need to store timestamps “in UTC”. You just need to store the time zone offset. That extra few bytes of precision representing where the timestamp sender is makes the sun location absolute.
Some databases let you input values like “2022-03-13T08:33:26-06:00” and then display them in UTC or your local time zone or whatever time zone you configured. BugQuery at one time was toying with the idea of taking a few additional bytes of information to represent the preferred display timezone of the timestamp, but I have no idea if that ever made it to beta.
- HideousKojima 5y agoThat won't work for everything. For example: 1) User schedules a meeting 6 months out. Their time zone is -5 from UTC 2) 3 months later, their local politicians change their timezone to be -4.5 from UTC 3) The database has the wrong time since it has -5 stored and people miss the meeting by 30 minutes