Re: bug in jsonb_set porstgresql 5.5

From: Thomas Kellerer <spam_eater(at)gmx(dot)net>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: bug in jsonb_set porstgresql 5.5
Date: 2018-02-22 15:51:13
Message-ID: p6mopi$vc8$1@blaine.gmane.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Pascal Barbedor schrieb am 22.02.2018 um 14:38:
> 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
>
> Those three instructions were sent to postgresql
>
> 1- this one is ok, set the field to an empty object
> *update table1 set history=‘{}’*
>
> 2- this one is ok, creates a key q1 initialized at an empty object
> *update table1 set history=jsonb_set(history,’{q1}’, ‘{}’)*
>
> *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))*
>
> this is on postgresql 5.5

There is no PostgreSQL 5.5 (and never was if I'm not mistaken)

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Pascal Barbedor 2018-02-22 15:51:15 Re: bug in jsonb_set postgresql 5.5
Previous Message David G. Johnston 2018-02-22 15:42:27 Re: bug in jsonb_set porstgresql 5.5