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

David E. Wheeler <david@justatheory.com>

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

To: "David G. Johnston" <david.g.johnston@gmail.com>

Cc: andrew@dunslane.net, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-06-12T20:10:01Z

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

On Jun 12, 2024, at 4:02 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:

> Adding Andrew.

Thank you.

> I'm willing to call this an open item against this feature as I don't see any documentation explaining that string() behaves differently than the others.

Maybe there’s some wording in the standard on this topic?

I’m happy to provide a patch to auto-unwrap .string() in lax mode. Seems pretty straightforward.

D