Re: Shouldn't jsonpath .string() Unwrap?

David E. Wheeler <david@justatheory.com>

From: "David E. Wheeler" <david@justatheory.com>

To: Chapman Flack <jcflack@acm.org>

Cc: Andrew Dunstan <andrew@dunslane.net>, "David G. Johnston" <david.g.johnston@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Jeevan Chalke <jeevan.chalke@enterprisedb.com>

Date: 2024-06-14T14:39:36Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Teach jsonpath string() to unwrap in lax mode
- 653d3969bb01 17.0 landed

Attachments

v1-0001-Teach-jsonpath-string-to-unwrap-in-lax-mode.patch (application/octet-stream) patch v1-0001

On Jun 13, 2024, at 21:55, Chapman Flack <jcflack@acm.org> wrote:

> My opinion is yes, that should be done. 9.46, umm, General
> Rule 11 g ii 6) A) says just "if MODE is lax and <JSON method> is not
> type or size, then let BASE be Unwrap(BASE)." No special exemption
> there for string(), nor further below at C) XV) for the operation
> of string().

Thank you! Cited that bit in the commit message in the attached patch (also available as a GitHub PR[1]).

D

[1]: https://github.com/theory/postgres/pull/5