| From: | Marko Tiikkaja <marko(at)joh(dot)to> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com>, Ryan Pedela <rpedela(at)datalanche(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Geoghegan <pg(at)heroku(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 20:15:33 |
| Message-ID: | 555A4865.6030109@joh.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2015-05-18 22:10, Josh Berkus wrote:
> On 05/18/2015 01:04 PM, Ryan Pedela wrote:
>> In the context of splitting shallow and deep merge into two operators, I
>> think + is better for shallow and || better for deep. The reason for +
>> is because many programming languages have this behavior. If I see the
>> below code in language I have never used before:
>>
>> objC = objA + objB
>>
>> My default assumption is that + performs a shallow merge. Like I said, I
>> would rather there just be one operator.
>
> Thank you, that helps. Anyone else?
If everyone thinks the operators mean different things, we could just
not add any operators and only provide functions instead.
.m
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-05-18 20:17:46 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Josh Berkus | 2015-05-18 20:10:44 | Re: jsonb concatenate operator's semantics seem questionable |