4 ms·
That's very much a time with a timezone (the timezone being the place where the event happens). However it's not a postgres "timestamp with timezone", which (a
by masklinn 8y ago
That's very much a time with a timezone (the timezone being the place where the event happens).
However it's not a postgres "timestamp with timezone", which (as both TFA and fphilipe's article note) doesn't store a timezone.
The problem of "future event in a local place" is why the "store everything as UTC" trend is wrong, incidentally: if the timezone's offset changes (which happens regularly, sometimes with very little warning) the stored time is now completely off, by minutes to days[0] depending on the change. "Store everything as UTC" is only suitable if you're only ever storing past events (timezones don't normally get retroactively altered).
[0] https://www.timeanddate.com/news/time/samoa-dateline.html https://www.timeanddate.com/news/time/samoa-dateline.html