Re: pgsql: Add a non-strict version of jsonb_set - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Add a non-strict version of jsonb_set
Date
Msg-id 13104.1580311731@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Add a non-strict version of jsonb_set  (Michael Paquier <michael@paquier.xyz>)
List pgsql-committers
Michael Paquier <michael@paquier.xyz> writes:
> On Wed, Jan 29, 2020 at 09:54:23AM +0100, Magnus Hagander wrote:
>> We'd also have to come to this magic actual agreement on which such
>> fields we *want* :)  Which alone would be an improvement.

> Well, there has been some discussion about this matter on the lists
> not so long ago:
> https://www.postgresql.org/message-id/CABUevEzauoMm3irCyg4s=vUX5hUcKmTW_R69fiKS4+72gzyAOw@mail.gmail.com
> https://www.postgresql.org/message-id/CA+hUKGJR+YtZUdq9_6cFsqCRH_fvfumdDZgmiLwXBHCrTJUGmw@mail.gmail.com
> And it seems to me that the only consensus we reached was about having
> "Discussion:", while the other tags were not that popular.

Yeah, that's my understanding of the state of affairs too:
a Discussion: link is expected if relevant, but whether you want to
express other info as a tag or free text is committer's choice.

            regards, tom lane



pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: pgsql: Move jsonapi.c and jsonapi.h to src/common.
Next
From: Robert Haas
Date:
Subject: pgsql: Add jsonapi.c to Mkvcbuild.pm's @pgcommonallfiles.