Re: Add jsonb_translate(jsonb, from, to)

On 29.09.25 14:34, Florents Tselai wrote:
>> Cannot be better to use JsonPath for specification what should be 
>> replaced?
> 
> Fair point.
> The main purpose of this patch is to provide a recursive, global 
> replacement across all values and arrays,
> which is not as straightforward to express in JSONPath today.
> I understand that some may find this too case-specific, so I’m just 
> leaving it out there for consideration.
> That said, I believe it can be quite useful in domains where documents 
> carry many tags or labels that need to be translated or normalized 
> consistently.

Oracle has a json_transform function, which has also been added to the 
SQL standard draft recently.  That appears to be more in the direction 
that Pavel is suggesting.  Maybe someone wants to take a stab at it. 
(In that case, having both a json_transform and a json_translate might 
be confusing.)