| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:45:21 |
| Message-ID: | 555CE451.7060607@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05/20/2015 03:34 PM, Tom Lane wrote:
> 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>
Yeah, I knew they were pretty old.
When did the SQL standard add any mention of ?
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-05-20 19:52:07 | Re: anole: assorted stability problems |
| Previous Message | Alvaro Herrera | 2015-05-20 19:44:12 | Re: anole: assorted stability problems |