| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Chris BSomething <xpusostomos(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Inconsistency of timezones in postgresql |
| Date: | 2024-07-31 17:42:09 |
| Message-ID: | CAKFQuwY_k7=GGPzOHLuN7dPxHKsR0sLBQPNSaaynuSKWCVOTsg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Wednesday, July 31, 2024, Chris BSomething <xpusostomos(at)gmail(dot)com> wrote:
> Tom Lane said:
> "However, notice that the value following TIME ZONE is only allowed to
> be an interval by the spec (and this is still true in SQL:2021,
> the latest version I have handy). Such an interval is interpreted per
> ISO (positive = east of Greenwich)."
>
> Erm, what do you mean by an interval? If you mean a number, then it’s
> broken, because "UTC+10" and "+10" do the same thing. But you seem to be
> saying there is indeed some syntax that is interpreted by ISO logic?
>
There is a named data type called “interval”. He’s referring to that.
Neither of those text values is an interval. ‘4 hours 30
minutes’::interval is a relevant example.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris BSomething | 2024-07-31 19:03:03 | Re: Inconsistency of timezones in postgresql |
| Previous Message | Chris BSomething | 2024-07-31 17:14:56 | Re: Inconsistency of timezones in postgresql |