Tom Lane writes:
> Even though I think '|' is clearly given a bogus precedence, I doubt
> it's a good idea to change it.
The only builtin '|' operator, besides the not-there-yet bitor, is some
arcane prefix operator for the "tinterval" type, which returns the start
of the interval. This is all long dead so that would perhaps give us a
chance to change this before we add "or" operators. That might weigh more
than the possibility of a few users having highly specialized '|'
operators that rely on this precedence.
The tinterval type has pretty interesting parsing rules, btw.:
peter=# select 'whatever you say'::tinterval;
?column?
-----------------------------------------------------
["1935-12-23 09:42:00+01" "1974-04-16 17:52:52+01"]
(1 row)
--
Peter Eisentraut [EMAIL PROTECTED] http://yi.org/peter-e/
