Re: jsonb concatenate operator's semantics seem questionable

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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>, Ryan Pedela <rpedela(at)datalanche(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-21 14:15:59
Message-ID: CA+TgmoZjvnE=t41k5PCPfcroSthOME34WcB2Dyctx=rSQjqkEQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, May 20, 2015 at 3:42 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-05-20 15:37:15 -0400, Tom Lane wrote:
>> Josh Berkus <josh(at)agliodbs(dot)com> writes:
>> > 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?
>>
>> I think this could be seen as a correction/bug fix for a pre-freeze
>> feature. We should not be too resistant to filing down rough edges
>> on new features, even if that involves a spec change.
>
> +1

+1, emphatically.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleksandr Shulgin 2015-05-21 14:48:20 Re: pg_dump quietly ignore missing tables - is it bug?
Previous Message Robert Haas 2015-05-21 14:11:16 Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)