pgsql: Declare range inclusion operators as taking anyelement not anyno

Started by Tom Laneover 14 years ago1 messagescomitters

tgl@sss.pgh.pa.us

over 14 years ago

Declare range inclusion operators as taking anyelement not anynonarray.

Use of anynonarray was a crude hack to get around ambiguity versus the
array inclusion operators of the same names. My previous patch to extend
the parser's type resolution heuristics makes that unnecessary, so use
the more general declaration instead. This eliminates a wart that these
operators couldn't be used with ranges over arrays, which are otherwise
supported just fine.

Also, mark range_before and range_after as commutator operators,
per discussion with Jeff Davis.

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/709aca59608395eef9ceb7dcb79fd9d03a0709ef

Modified Files
--------------
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_amop.h | 4 ++--
src/include/catalog/pg_operator.h | 8 ++++----
src/include/catalog/pg_proc.h | 4 ++--
src/test/regress/expected/rangetypes.out | 12 ++++++++++++
src/test/regress/sql/rangetypes.sql | 3 +++
6 files changed, 24 insertions(+), 9 deletions(-)