| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | Kevin Grittner <kgrittn(at)ymail(dot)com>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Jan de Visser <jan(at)de-visser(dot)net>, "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-20 19:34:00 |
| Message-ID: | 2705.1432150440@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dave Cramer <pg(at)fastcrypt(dot)com> writes:
> Notably absent from the discussion is ODBC upon which JDBC was modelled and
> probably predates any use of ? as an operator
<historical-nitpicking>
It would be a mistake to imagine that operators containing '?' are some
johnny-come-lately. The <?> operator for tintervals can be traced back
at least to Postgres v4r2 (1994), which is the oldest tarball I have at
hand. Most of the current list are geometric operators that were added
by Tom Lockhart in 1997. The only ones that aren't old enough to vote
are the JSONB ones we added last year.
Not that the problem's not real, but these operators predate any attempt
to make Postgres work with ODBC or JDBC or any other connector. Otherwise
we might've thought better of using '?'.
</historical-nitpicking>
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-05-20 19:37:15 | Re: jsonb concatenate operator's semantics seem questionable |
| Previous Message | Robert Haas | 2015-05-20 19:23:49 | Re: RFC: Non-user-resettable SET SESSION AUTHORISATION |