Re: Document DateStyle effect on jsonpath string()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter@eisentraut.org>
Cc: "David E. Wheeler" <david@justatheory.com>,
jian he <jian.universality@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-09-10T20:16:12Z
Lists: pgsql-hackers
Peter Eisentraut <peter@eisentraut.org> writes: > These JSON path functions are specified by the SQL standard, so they > shouldn't depend on PostgreSQL-specific settings. At least in new > functionality we should avoid that, no? Hmm ... but does the standard precisely define the output format? Since these conversions are built on our own timestamp I/O code, I rather imagine there is quite a lot of behavior there that's not to be found in the standard. That doesn't really trouble me as long as the spec's behavior is a subset of it (i.e., reachable as long as you've got the right parameter settings). regards, tom lane
Commits
-
Make jsonpath .string() be immutable for datetimes.
- cc4fdfa411fa 17.0 landed
- cb599b9ddfcc 18.0 landed
-
Improve documentation and testing of jsonpath string() for datetimes.
- ed055d249df5 18.0 landed