From: | Tim Field <tim(at)mohiohio(dot)com> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Comparing date strings with jsonpath expression |
Date: | 2023-05-26 01:36:14 |
Message-ID: | 014A028B-5CE6-4FDF-AC24-426CA6FC9CEE@mohiohio.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
When using .datetime() in jsonpath expressions JSON encoded dates are not parsed, this is coupled with the fact that an error isn’t reported.
I would expect that any date encoded via JSON.stringify() would be parseable in these JSON path functions as that is after all the format that dates are very likely to be in.
If I JSON encode a date I get a value such as "2023-05-22T03:09:37.825Z” .datetime() fails to parse this due to the mircosends and timezone indicator, yet its possible to convert that with
"2023-05-22T03:09:37.825Z”::timestamptz
Example here of the issue, and a stackoverflow post with further discussion.
https://stackoverflow.com/questions/76319993/comparing-date-strings-with-jsonpath-expression
Comparing date strings with jsonpath expression
stackoverflow.com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-05-26 05:48:30 | Re: BUG #17942: vacuumdb doesn't populate extended statistics on partitioned tables |
Previous Message | Kyotaro Horiguchi | 2023-05-26 00:15:36 | Re: BUG #17942: vacuumdb doesn't populate extended statistics on partitioned tables |