Re: jsonb concatenate operator's semantics seem questionable - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: jsonb concatenate operator's semantics seem questionable
Date
Msg-id CAM3SWZQBu-Wan=9opvJVSy2isztm-y6UeeDg_mccrfqiqe-kug@mail.gmail.com
Whole thread Raw
In response to Re: jsonb concatenate operator's semantics seem questionable  (Catalin Iacob <iacobcatalin@gmail.com>)
List pgsql-hackers
On Mon, May 18, 2015 at 1:19 PM, Catalin Iacob <iacobcatalin@gmail.com> wrote:
> In hstore @> means unnested containment, in jsonb it means nested
> containment. Therefore, when an hstore operator is applied to jsonb it gets
> "nestedness" as jsonb is nested and adds that nestedness is an important
> thing that sets it apart from hstore. Therefore, since || is unnested
> concatenation in hstore, it should become nested concatenation for jsonb.
>
> I don't know if the argument is strong enough but it does make some sense.

Right. And I'm not saying that there isn't a place for shallow
containment, or whatever you want to call it. But I prefer to do that
with an operator that people haven't been taught to think of as "the
update operator" from hstore.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Catalin Iacob
Date:
Subject: Re: jsonb concatenate operator's semantics seem questionable
Next
From: Alvaro Herrera
Date:
Subject: Re: ERROR: cannot GetMultiXactIdMembers() during recovery