Re: jsonb concatenate operator's semantics seem questionable - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: jsonb concatenate operator's semantics seem questionable
Date
Msg-id CAFj8pRArpHki3Yw5ovxGDgb6Pd5=V3gEPibtwAXp5SHDF0rL-w@mail.gmail.com
Whole thread Raw
In response to Re: jsonb concatenate operator's semantics seem questionable  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers

It is like bugfix than new feature

Dne 20.5.2015 21:08 napsal uživatel "Josh Berkus" <josh@agliodbs.com>:
On 05/20/2015 11:34 AM, Andrew Dunstan 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.

That does cover all bases, and users would be able to create the
operator which suits their particular use case easily.  It's also fairly
similar to how jsquery works, although the syntax is completely different.

But ... it's after feature freeze.  So, thoughts?

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: GROUPING
Next
From: Alvaro Herrera
Date:
Subject: anole: assorted stability problems