| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Ryan Pedela <rpedela(at)datalanche(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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:45:03 |
| Message-ID: | 555A332F.8020809@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-18 18:50:05 | Re: upper planner path-ification |
| Previous Message | Peter Geoghegan | 2015-05-18 18:34:30 | Re: jsonb concatenate operator's semantics seem questionable |