Re: jsonb_set() strictness considered harmful to data - Mailing list pgsql-general

From Mark Felder
Subject Re: jsonb_set() strictness considered harmful to data
Date
Msg-id 2a60e719-0c93-4d68-a94d-436fcd928d3d@www.fastmail.com
Whole thread Raw
In response to Re: jsonb_set() strictness considered harmful to data  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
List pgsql-general

On Mon, Oct 28, 2019, at 08:52, Andrew Dunstan wrote:
> 
> For release 13+, I have given some more thought to what should be done.
> I think the bar for altering the behaviour of a function should be
> rather higher than we have in the present case, and the longer the
> function has been sanctioned by time the higher the bar should be.
> However, I think there is a case to be made for providing a non-strict
> jsonb_set type function. To advance th4e discussion, attached is a POC
> patch that does that. This can also be done as an extension, meaning
> that users of back branches could deploy it immediately. I've tested
> this against release 12, but I think it could go probably all the way
> back to 9.5. The new function is named jsonb_ set_lax, but I'm open to
> bikeshedding.
> 
> 

Thank you Andrew, and I understand the difficulty in making changes to functions that already exist in production
deployments.An additional function like this would be helpful to many.
 


-- 
  Mark Felder
  ports-secteam & portmgr alumni
  feld@FreeBSD.org



pgsql-general by date:

Previous
From: "Basques, Bob (CI-StPaul)"
Date:
Subject: Re: SQL pretty pritner?
Next
From: Yessica Brinkmann
Date:
Subject: Re: I think that my data is saved correctly, but when printing again,other data appears