From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: IN, BETWEEN, spec compliance, and odd operator names |
Date: | 2008-08-25 14:17:19 |
Message-ID: | 200808251717.19878.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Monday 25 August 2008 04:24:23 Tom Lane wrote:
> Seems to me that what this boils down to is whether we want to read the
> spec literally ("it says the construct is defined in terms of operators
> named >= and <=, therefore we should do that") or by intent (obviously
> what they *want* is a construct that behaves sensibly in terms of the
> datatype's semantics).
I would be generally in favor of moving more toward a semantics-based approach
instead of a name-based approach.
It would be interesting to see an enumeration of all the parts of the system
that hardcode operator names. Based on that we might gain more insight into
what it would take to go one way or another.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-08-25 14:43:30 | Re: IN, BETWEEN, spec compliance, and odd operator names |
Previous Message | Alvaro Herrera | 2008-08-25 13:48:04 | Re: can't stop autovacuum by HUP'ing the server |