"TIMESTAMP and TIME may also be specified as being WITH TIME ZONE, in which case every value has associated with it a time zone displacement. In comparing values of a data type WITH TIME ZONE, the value of the time zone displacement is disregarded." Well what's the point then?
-
-
I'd actually like to understand the long version. Timestamps and timezones are the bane of client interface authors!
-
The long version of how the spec defines timezones is: a "timezone" is actually just a UTC offset. There are no zone names, DST boundaries, historical zone changes etc. A timestamp with time zone is a UTC timestamp and an offset.
- 5 more replies
New conversation -
-
-
In the spec, timestamp comparison is defined roughly as: convert everything to local time, subtract to give an interval in terms of the smallest time unit present, and compare that against 0 to determine less/equal/greater
-
If you're thinking "but DST...?" then you have observed one of the reasons why
@PostgreSQL does not follow the spec in this area; the spec has no concept of DST
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.