From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Document DateStyle effect on jsonpath string() |
Date: | 2024-09-11 16:06:27 |
Message-ID: | 3832087.1726070787@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"David E. Wheeler" <david(at)justatheory(dot)com> writes:
> On Sep 11, 2024, at 11:11, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> What "let result be stringified" behavior are you thinking of,
>> exactly? AFAICS there's not sensitivity to timezone unless you
>> use the _tz variant, otherwise it just regurgitates the input.
> There is stringification of a time, date, or timestamp value, which
> has no TZ, but is still affected by DateStyle.
What I understood you to be referencing is what happens without
string(), which AFAICS does not result in any timezone rotation:
regression=# set timezone = 'America/New_York';
SET
regression=# select jsonb_path_query('"2023-08-15 12:34:56-09"', '$.timestamp_tz()');
jsonb_path_query
-----------------------------
"2023-08-15T12:34:56-09:00"
(1 row)
I think I'd be content to have string() duplicate that behavior
--- in fact, it seems like it'd be odd if it doesn't match.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2024-09-11 16:26:42 | Re: Document DateStyle effect on jsonpath string() |
Previous Message | David E. Wheeler | 2024-09-11 15:52:31 | Re: Document DateStyle effect on jsonpath string() |