| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | 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 18:58:55 |
| Message-ID: | 555A366F.1070408@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/18/2015 02:45 PM, Josh Berkus wrote:
> On 05/18/2015 11:34 AM, Peter Geoghegan wrote:
>> I'm not necessarily attached to "+". I just want to make this
>> different to hstore's "||" operator. There should be a similar idiom
>> with jsonb, but that can come later.
> This argument still makes no sense to me. Hstore is not nested. If
> anything, the behavior of || in hstore suggests that we *should* use ||
> for shallow append in JSONB.
>
Yeah, I agree. To me "concatenation" seems a wrong designation of what
is effectively a recursive merge.
I have no objection to us making much clearer in the docs exactly what's
happening with ||.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-05-18 19:12:33 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Peter Geoghegan | 2015-05-18 18:58:39 | Re: jsonb concatenate operator's semantics seem questionable |