Re: bug in jsonb_set postgresql 5.5
| От | Pascal Barbedor |
|---|---|
| Тема | Re: bug in jsonb_set postgresql 5.5 |
| Дата | |
| Msg-id | AA261343-E741-4E6B-98F1-6496B3A44795@blset.com обсуждение исходный текст |
| Ответ на | Re: bug in jsonb_set porstgresql 5.5 ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Список | pgsql-bugs |
Thanks for the answer
Where is this mentioned in the doc ?
Since it is only a key inside the json object which is assigned the null value, does it mean it is impossible to have null values inside the jsonb object ?
Le 22 févr. 2018 à 16:42, David G. Johnston <david.g.johnston@gmail.com> a écrit :HelloI 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 nullupdate 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.
В списке pgsql-bugs по дате отправления: