Re: jsonb_set() strictness considered harmful to data - Mailing list pgsql-general

From Maciek Sakrejda
Subject Re: jsonb_set() strictness considered harmful to data
Date
Msg-id CAOtHd0DK=9bc6uBqt+hmfjkWj-EoUivf6rDZpnK8b2xswnrfcQ@mail.gmail.com
Whole thread Raw
In response to Re: jsonb_set() strictness considered harmful to data  (Stuart McGraw <smcg4191@mtneva.com>)
List pgsql-general
On Wed, Oct 23, 2019 at 12:01 PM Stuart McGraw <smcg4191@mtneva.com> wrote:
> Why the inconsistency between the array
> type and json type?  Are there any cases other than json where the entire
> compound value is set to NULL as a result of one of its components being
> NULL?

That's a great point. It does look like hstore's delete / minus
operator behaves like that, though:

=# select 'a=>1,b=>2'::hstore - null;
 ?column?
----------

(1 row)



pgsql-general by date:

Previous
From: Rob Sargent
Date:
Subject: Re: Composite type storage overhead
Next
From: rob stone
Date:
Subject: Re: jsonb_set() strictness considered harmful to data