| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Geoff Winkless <gwinkless(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: jsonb problematic operators |
| Date: | 2016-12-12 15:00:04 |
| Message-ID: | CAMsr+YG6j0gLCxpa+AmWMN8_SUO=jK4VtP5MLhE-MACxW0SZ+A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12 Dec. 2016 22:22, "Merlin Moncure" <mmoncure(at)gmail(dot)com> wrote:
If we really wanted to fix this, maybe the right way
to think about the problem is a highly reduced character set and a
pre-processor or an extension.
I'm pretty OK with expecting client drivers not to be stupid and offer
escape syntax for their placeholders. I was kind of astonished the jdbc
spec doesn't given how hard it works to be compatible. I'd assumed the ??
was jdbc standard not a postgres extension until I looked into it.
Certainly PDO needs a patch for its postgres driver if not (preferably) to
support escaping at a higher level.
Users can work around it by defining their own operator aliases + opclasses
or using function forms.
Doesn't seem worth too much drama though it sucks for usability.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2016-12-12 15:02:59 | Re: background sessions |
| Previous Message | Ian Jackson | 2016-12-12 14:45:21 | Re: [OSSTEST PATCH 0/1] PostgreSQL db: Retry on constraint violation |