←back to thread

Timestamps and Time Zones in PostgreSQL (2016)

(phili.pe)
189 points GordonS | 3 comments | 30 Mar 19 21:47 UTC | HN request time: 0.582s | source
Show context
welder ◴[31 Mar 19 05:51 UTC] No.19534121[source]▶
> A Valid Use Case For timestamp without time zone

This should be "A Valid Use Case For timestamp with time zone".

This article gets it all wrong. The only time it's acceptable to store time with time zone is DATES that do not have a TIME component.

replies(1): >>19534300 #
1. groestl ◴[31 Mar 19 07:05 UTC] No.19534300[source]▶
I'm probably just misunderstanding, but a calendar like Google Calendar definitely needs to store time with a time zone (i.e. dates with a time component). This allows to keep a scheduled event at 9 AM, even if the time zone offset is redefined (due to a political event).
replies(2): >>19534405 #>>19535029 #
2. alboy ◴[31 Mar 19 07:45 UTC] No.19534405[source]▶
Or some of the schedulees of the events move across time zones. There're absolutely other use cases.
3. welder ◴[31 Mar 19 11:27 UTC] No.19535029[source]▶
Oh, yea I forgot scheduling. All other cases you should use utc.