Re: JSONB Overlap Operator.

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Eduardo Felipe <edufelipe(at)e3c(dot)com(dot)br>
Cc: PostgreSQL General <pgsql-general(at)postgresql(dot)org>
Subject: Re: JSONB Overlap Operator.
Date: 2017-03-20 18:58:27
Message-ID: CAHyXU0wc22mACuY2H3JKV95D6q-804UM4b+xOBbBEMRGX5GwEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Mar 17, 2017 at 9:43 AM, Eduardo Felipe <edufelipe(at)e3c(dot)com(dot)br> wrote:
> Hi there!
>
> In a project I was experimenting with replacing array columns with JSONB
> columns, to allow a greater flexibility of types.
>
> One thing that I found missing is the "overlap" operator (&&).
>
> JSONB includes all other operators from arrays, such as containment (@>,
> <@), comparison (>, >=, <, <=) and inclusion (?). The only one missing is
> the overlap operator (&&).
>
> Does anyone know of a technical reason that operator was not included on
> JSONB?

I really miss hstore slice() (which is a function, not an operator,
but the distinction is is minor IMO) where you can pass array of keys
and get a smaller object back. This would have to be redefined a bit
since there are new edge cases with jsonb vs hstore but it ought to be
reasonably worked out.

merlin

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Guyren Howe 2017-03-20 19:32:11 Advice about software engineering inside Postgres?
Previous Message ibeq GmbH 2017-03-20 17:28:53 Why is this functional index not used?