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

David E. Wheeler <david@justatheory.com>

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

To: Jeevan Chalke <jeevan.chalke@enterprisedb.com>

Cc: Chapman Flack <jcflack@acm.org>, Andrew Dunstan <andrew@dunslane.net>, "David G. Johnston" <david.g.johnston@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2024-06-15T14:39:06Z

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 15, 2024, at 10:27, Jeevan Chalke <jeevan.chalke@enterprisedb.com> wrote:

> Sorry, I have missed this in the original patch. I am surprised how that happened. But thanks for catching the same and fixing it.

No worries. :-)

> The changes are straightforward and look good to me. However, I have kept the existing test of an empty array as is, assuming that it is one of the valid tests. It now returns zero rows instead of an error. Your added test case covers this issue.

Makes sense, thank you.

D