Re: Shouldn't jsonpath .string() Unwrap? - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: Shouldn't jsonpath .string() Unwrap?
Date
Msg-id 06E27A26-413B-4580-889D-A6E5CE16566A@justatheory.com
Whole thread Raw
In response to Re: Shouldn't jsonpath .string() Unwrap?  (Jeevan Chalke <jeevan.chalke@enterprisedb.com>)
Responses Re: Shouldn't jsonpath .string() Unwrap?
List pgsql-hackers
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
andfixing 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,
assumingthat it is one of the valid tests. It now returns zero rows instead of an error. Your added test case covers
thisissue. 

Makes sense, thank you.

D




pgsql-hackers by date:

Previous
From: Jeevan Chalke
Date:
Subject: Re: Shouldn't jsonpath .string() Unwrap?
Next
From: Andrew Dunstan
Date:
Subject: Re: RFC: adding pytest as a supported test framework