Re: BUG #15075: jsonb_set return [null] if new value is null but not 'null'.

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: claudel(dot)sylvain(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15075: jsonb_set return [null] if new value is null but not 'null'.
Date: 2018-02-19 09:18:23
Message-ID: 20180219091823.GA42340@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Feb 19, 2018 at 08:33:49AM +0000, PG Bug reporting form wrote:
> Is this behavior normal ?
>
> select jsonb_set('{"f1":1,"f2":null,"f3":"bidule"}', '{f3}', null, false);
> #> [null]
> select jsonb_set('{"f1":1,"f2":null,"f3":"bidule"}', '{f3}', 'null',
> false);
> #> {"f1":1,"f2":null,"f3":null}
>
> In a update query, it is dangerous.
> It may be better that the request crashes rather than executing with
> surprising behavior.

jsonb_set is a strict function, meaning that any NULL value from input
arguments will make the function return NULL as result, which is what
your first example does. In the second query, you are using null as
JSON value, which is actually valid as input. So as far as I can see,
this is normal.

> Sorry if this report is not "clean".

No problem. I have been able to decrypt it easily :)
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2018-02-19 09:21:52 Re: BUG #15074: psql client never returns when creating index (long running operation)
Previous Message PG Bug reporting form 2018-02-19 08:33:49 BUG #15075: jsonb_set return [null] if new value is null but not 'null'.