Re: Unexpected behavior of jsonb_set() with a `null` value - Mailing list pgsql-bugs

From Thomas Kellerer
Subject Re: Unexpected behavior of jsonb_set() with a `null` value
Date
Msg-id db9745f5-0d85-ed97-9911-9644957be2fc@gmx.net
Whole thread Raw
In response to Unexpected behavior of jsonb_set() with a `null` value  (Марк <kolypto@gmail.com>)
Responses Re: Unexpected behavior of jsonb_set() with a `null` value
List pgsql-bugs
Марк schrieb am 12.09.2019 um 12:55:
> With `jsonb_set()`, when `new_value` is `NULL`, the function would **erase the whole object**:
> 
> postgres=# SELECT jsonb_set('{"something":1}'::jsonb, '{language}', null, true);         
> jsonb_set  
> -----------
>  
> (1 row)
> 
> This is really dangerous for it may lead to data loss. Imaging the `new_value` argument being a function which
returns`NULL` values in some cases.
 
> The expected behavior is, perhaps, to convert an SQL `NULL` value to JSONB null value: 'null'::jsonb
> This way no data would be lost.
> 
> Or at the very least, this behavior should be documented.

I have asked the same: https://www.postgresql.org/message-id/flat/qfkua9%242q0e%241%40blaine.gmane.org

In short: not a bug ;) 




pgsql-bugs by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: BUG #16003: pg_basebackup failed with error : directory "xxxxxxx"exists but is not empty
Next
From: Tom Lane
Date:
Subject: Re: Unexpected behavior of jsonb_set() with a `null` value