From: | Jordan Gigov <coladict(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | jsonb problematic operators |
Date: | 2016-12-09 11:50:43 |
Message-ID: | CA+nBocB+DPnZRDB7JNvoTGuireM3BqJyz4sLqUCYT6tuM6SWfA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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.
It's not a good idea to expect everyone else to make for workarounds
for problems you choose to create.
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2016-12-09 12:01:20 | Re: `array_position...()` causes SIGSEGV |
Previous Message | Michael Paquier | 2016-12-09 11:10:41 | Re: Password identifiers, protocol aging and SCRAM protocol |