Re: jsonb concatenate operator's semantics seem questionable

<p dir="ltr">It is like bugfix than new feature<div class="gmail_quote">Dne 20.5.2015 21:08 napsal uživatel "Josh
Berkus"<<a href="mailto:josh@agliodbs.com">josh@agliodbs.com</a>>:<br type="attribution" /><blockquote
class="gmail_quote"style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 05/20/2015 11:34 AM, Andrew
Dunstanwrote:<br /> > So Dmitry, at my suggestion, has come up with a way of doing that, by<br /> > adding a
parameterto jsonb_replace(). If this parameter is set to true<br /> > (it defaults to false) and the key or array
elementpointed to by the<br /> > last element of the path doesn't exist, it gets created.<br /><br /> That does
coverall bases, and users would be able to create the<br /> operator which suits their particular use case easily. 
It'salso fairly<br /> similar to how jsquery works, although the syntax is completely different.<br /><br /> But ...
it'safter feature freeze.  So, thoughts?<br /><br /> --<br /> Josh Berkus<br /> PostgreSQL Experts Inc.<br /><a
href="http://pgexperts.com"target="_blank">http://pgexperts.com</a><br /><br /><br /> --<br /> Sent via pgsql-hackers
mailinglist (<a href="mailto:pgsql-hackers@postgresql.org">pgsql-hackers@postgresql.org</a>)<br /> To make changes to
yoursubscription:<br /><a href="http://www.postgresql.org/mailpref/pgsql-hackers"
target="_blank">http://www.postgresql.org/mailpref/pgsql-hackers</a><br/></blockquote></div>