| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | 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 03:41:44 |
| Message-ID: | 55595F78.8040604@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/17/2015 05:46 PM, Robert Haas wrote:
> On May 17, 2015, at 8:38 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>> The current behavior does not seem acceptable for the concatenate
>> operator ("operator || jsonb").
>
> I don't agree. It seems pretty clear to me after reading the new posts that the behavior is not an oversight, and that's enough for me to say that we should leave this alone.
Is there a particular reason why "+" makes more sense as "shallow
concatination" and "||" makes more sense as "deep concatination"? Like,
something in JS or other client languages which would make that
preference make more sense to users?
While I hate last-minute changes in general, once we have this
functionality as || we won't be able to swap operators later if we
decide that deep concatination should have been ||. So I want to be
clear on why users will prefer that to + .
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2015-05-18 03:58:45 | Re: Disabling trust/ident authentication configure option |
| Previous Message | Josh Berkus | 2015-05-18 03:35:49 | Re: 9.5 open items |