| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Pascal Barbedor <pbarbedor(at)blset(dot)com> |
| Cc: | Postgres Bug <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: bug in jsonb_set porstgresql 5.5 |
| Date: | 2018-02-22 15:42:27 |
| Message-ID: | CAKFQuwYSLegY5M45SeOaVw_HmAavJPij7-xtwOS=bZjwTgXBVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Feb 22, 2018 at 6:38 AM, Pascal Barbedor <pbarbedor(at)blset(dot)com>
wrote:
> Hello
>
>
> I noticed a problem with a jsonb field and jsonb_set function
>
>
> - table1 is a table with *history* a jsonb field, and *obs* a text field
> which is null
>
> [...]
> *3- this one resets completely the jsonb field, not only the key obs is
> not set to null but the entire jsonb field is now null*
>
> *update table1 set history=jsonb_set(history,’{q1,obs}’, to_jsonb(obs))*
>
Working as designed - jsonb_set and to_jsonb are both defined as "NULL ON
NULL INPUT (i.e., STRICT)" - since "obs [is] a text field which is null"
the final result of the function call is NULL.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2018-02-22 15:51:13 | Re: bug in jsonb_set porstgresql 5.5 |
| Previous Message | Tom Lane | 2018-02-22 15:12:22 | Re: BUG #15076: postmaster crashes unexpectedly when using up arrow key in psql command |