From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Greg Sabino Mullane <greg(at)turnstep(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Problems with question marks in operators (JDBC, ECPG, ...) |
Date: | 2015-05-17 21:36:20 |
Message-ID: | CAKFQuwag-AAxXVcCatpkYjegwpsYAkeFKL_spuXsfs_8rWjABQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, May 17, 2015 at 9:15 AM, Greg Sabino Mullane <greg(at)turnstep(dot)com>
wrote:
> Dave Cramer wrote:
> > Well our solution was to use ?? but that does mean we have to do some
> > extra parsing which in a perfect world wouldn't be necessary.
>
> That's not a good solution as '??' is a perfectly valid operator. ISTR
> seeing it used somewhere in the wild, but I could be wrong.
>
>
It which case you would write (I think, not tested and not part of the
test suite that I can see...):
a ???? b ...
There was some discussion about ?? vs \?:
https://github.com/pgjdbc/pgjdbc/pull/187
I did find some alternatives discussed a couple of years back, like
{postgres qm} and <operator("?")>; the later simply being to allow the
operator to be quoted inside "operator()"
http://postgresql.nabble.com/Alias-hstore-s-to-so-that-it-works-with-JDBC-td5743863i20.html
The commit that added "??":
https://github.com/pgjdbc/pgjdbc/pull/227
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2015-05-17 21:44:28 | Re: jsonb concatenate operator's semantics seem questionable |
Previous Message | Robert Haas | 2015-05-17 20:23:08 | Re: WALWriteLock contention |