Re: jsonb problematic operators

From: Geoff Winkless <pgsqladmin(at)geoff(dot)dj>
To: Jordan Gigov <coladict(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: jsonb problematic operators
Date: 2016-12-09 12:10:17
Message-ID: CAEzk6fc9uCYu4pB0E9TLb_Lsdd=WBTkkRQ66TMr9_-naFkgb6g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9 December 2016 at 11:50, Jordan Gigov <coladict(at)gmail(dot)com> wrote:
> There is this problem with the jsonb operators "? text" "?| text[]"
> and "?& text[]" that the question mark is typically used for prepared
> statement parameters in the most used abstraction APIs in Java and
> PHP.
>
> This really needs an alternative. Something like "HAS text", "HAS
> ANY(text[])" and "HAS ALL(text[])" same as regular array usage. It
> probably should be another word that has less chance of becoming a
> conflict with another operator in future SQL specifications, but
> that's for you to decide.

You mean something like the jsonb_ functions ?

\df jsonb*

> It's not a good idea to expect everyone else to make for workarounds
> for problems you choose to create.

I'd say it's not a good idea to come asking questions of a mailing
list with an attitude like that, but hey, it's nearly Holidays.

Geoff

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2016-12-09 12:11:43 Re: Declarative partitioning - another take
Previous Message Alvaro Herrera 2016-12-09 12:01:20 Re: `array_position...()` causes SIGSEGV