Re: Document DateStyle effect on jsonpath string()
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David E. Wheeler" <david@justatheory.com>
Cc: jian he <jian.universality@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-09-10T18:51:48Z
Lists: pgsql-hackers
"David E. Wheeler" <david@justatheory.com> writes: > Rebase on 47c9803. I also changed the commitfest item[1] to “ready for committer”, since jian reviewed it, though I couldn’t see a way to add jian as a reviewer in the app. Hope that makes sense. Pushed with a little additional polishing. I thought the best way to address jian's complaint about DateStyle not being clearly locked down was to change horology.sql to verify the prevailing setting, as it has long done for TimeZone. That's the lead test script for related stuff, so it makes the most sense to do it there. Having done that, I don't feel a need to duplicate that elsewhere. 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