On 10/29/2018 04:18 PM, Vik Fearing wrote:
A use case that I see quite a lot of is needing to do reports and other
calculations on data per day/hour/etc but in the user's time zone. The
way to do that is fairly trivial, but it's not obvious what it does so
reading queries becomes just a little bit more difficult.
Hm, I am not sure if I see any major win from writing
date_trunc('day', timestamptz '2001-02-16 20:38:40+00', 'Australia/Sydney')
instead of
date_trunc('day', timestamptz '2001-02-16 20:38:40+00' AT TIME ZONE
'Australia/Sydney')
. Especially since you still will have to do the second for other time
related functions like date(). Maybe a slight win in that new users who
read the manual will be reminded that they need to care about time
zones, but I also see a value in teaching users about how to use "AT
TIME ZONE".
Andreas
