It depends. If something needs to happen in local time (like, always at the same time regardless of daylights savings for example) you should be storing times in local timezone
Yeah that’s true, tzid is probably better than just a straight offset, that’s probably what I was thinking but it was late when I posted lol. And the user moving is really more an issue of making updating that accessible imo
It depends. If something needs to happen in local time (like, always at the same time regardless of daylights savings for example) you should be storing times in local timezone
Store in UTC with the tz offset and if you’re using a modern tz library, that should handle it for you.
tz offset is really not enough. You’d need to save the time zone id and/or offset, to have you library calculate deviations such as daylight savings.
Even that, that would break if the user moves and now what they setup is using their previous timezone.
Basically, I’m saying that storing the offset works most of the time, but not all of the time.
Yeah that’s true, tzid is probably better than just a straight offset, that’s probably what I was thinking but it was late when I posted lol. And the user moving is really more an issue of making updating that accessible imo