From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: date_trunc() in a specific time zone |
Date: | 2018-10-29 15:26:31 |
Message-ID: | 7f0712c3-dad7-5aef-428e-db05a0a310df@proxel.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2018-10-29 15:32:21 | Re: PostgreSQL vs SQL/XML Standards |
Previous Message | Vik Fearing | 2018-10-29 15:18:23 | date_trunc() in a specific time zone |