Re: jsonb concatenate operator's semantics seem questionable

From: Ryan Pedela <rpedela(at)datalanche(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: Peter Geoghegan <pg(at)heroku(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(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-20 18:42:38
Message-ID: CACu89FQrozyJ0YNKsC2cA4bohDGdcwEa_q4-FYmCVUteyKLDyQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 20, 2015 at 12:34 PM, Andrew Dunstan <andrew(at)dunslane(dot)net>
wrote:

>
> So Dmitry, at my suggestion, has come up with a way of doing that, by
> adding a parameter to jsonb_replace(). If this parameter is set to true (it
> defaults to false) and the key or array element pointed to by the last
> element of the path doesn't exist, it gets created.
>

+1

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2015-05-20 18:44:14 Re: WIP: Enhanced ALTER OPERATOR
Previous Message Tom Lane 2015-05-20 18:41:49 Re: GROUPING