4 ms·
But a shop opening time is not a timestamp, so I think the original advice is still good. A timestamp is the time at which some event happened, which is differe
by wtetzner 6y ago
But a shop opening time is not a timestamp, so I think the original advice is still good. A timestamp is the time at which some event happened, which is different than a date/time used for specifying a schedule.
For example, if you wanted to track the history of when the shop actually opened, it would make sense to store a UTC timestamp.
- TheCoelacanth 6y ago> A timestamp is the time at which some event happened, which is different than a date/time used for specifying a schedule. Correct, but that makes this a rule with much more limited applications than many people are going to interpret it as.
- account42 6y agoYes, but scheduled times can look like timestamps. It might be tempting to store a date+time+location as just a UTC timestamps but timezones can and do change so the UTC timestamps for that scheduled time is not fixed.
- Joker_vD 6y agoAnd the time offset that was in effect when the event happened, allows you to easily answer questions like "Did the shop open late, i.e. after 10 AM local time?".
- dragonwriter 6y ago> A timestamp is the time at which some event happened, It's important to the advice to make explicit that the use of “timestamp” in that sense is intended, because “timestamp” is also in many contexts “the data type that combines date and time of day and, perhaps optionally, time zone information”. The application of “timestamps” in the latter sense is not limited to when they represent “timestamps” in the former sense.