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

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>
Cc: Chapman Flack <jcflack(at)acm(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Shouldn't jsonpath .string() Unwrap?
Date: 2024-06-15 14:39:06
Message-ID: 06E27A26-413B-4580-889D-A6E5CE16566A@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 15, 2024, at 10:27, Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2024-06-15 14:45:16 Re: RFC: adding pytest as a supported test framework
Previous Message Jeevan Chalke 2024-06-15 14:27:48 Re: Shouldn't jsonpath .string() Unwrap?