| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Catalin Iacob <iacobcatalin(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Ryan Pedela <rpedela(at)datalanche(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ilya Ashchepkov <koctep(at)gmail(dot)com> |
| Subject: | Re: jsonb concatenate operator's semantics seem questionable |
| Date: | 2015-05-18 20:21:54 |
| Message-ID: | CAM3SWZQBu-Wan=9opvJVSy2isztm-y6UeeDg_mccrfqiqe-kug@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, May 18, 2015 at 1:19 PM, Catalin Iacob <iacobcatalin(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-05-18 20:45:46 | Re: ERROR: cannot GetMultiXactIdMembers() during recovery |
| Previous Message | Catalin Iacob | 2015-05-18 20:19:34 | Re: jsonb concatenate operator's semantics seem questionable |