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

From Tom Lane
Subject Re: Unexpected behavior of jsonb_set() with a `null` value
Date
Msg-id 19278.1568298720@sss.pgh.pa.us
Whole thread Raw
In response to Re: Unexpected behavior of jsonb_set() with a `null` value  (Thomas Kellerer <spam_eater@gmx.net>)
List pgsql-bugs
Thomas Kellerer <spam_eater@gmx.net> writes:
> Марк schrieb am 12.09.2019 um 12:55:
>> The expected behavior is, perhaps, to convert an SQL `NULL` value to JSONB null value: 'null'::jsonb

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

There are other more-apropos threads in the archives, though I'm too
lazy to go find them right now.  IMO the problem here is an assumption
that SQL NULL should be interchangeable with a JSON NULL.  It's not,
and we don't intend to make it so, because (a) the definitional quagmire
that would result is bottomless; (b) people asking for this are generally
trying to use SQL NULL as a live data value, which is almost always just
a bad idea.

            regards, tom lane



pgsql-bugs by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: Unexpected behavior of jsonb_set() with a `null` value
Next
From: PG Bug reporting form
Date:
Subject: BUG #16006: Update queries fail on a table having any policy with a function that takes a whole-row var as arg