BUG #4809: Missing Expected Operator

Started by Paul Matthewsalmost 17 years ago2 messagesbugs
Jump to latest
#1Paul Matthews
plm@netspace.net.au

The following bug has been logged online:

Bug reference: 4809
Logged by: Paul Matthews
Email address: plm@netspace.net.au
PostgreSQL version: 8.3.7
Operating system: Linux OpenSuse 11.0
Description: Missing Expected Operator
Details:

Not a bug as such, but an obvious operator is missing.

WHERE
g.box_boundary @> w.geocode and
ERROR: operator does not exist: box @> point
g.boundary @> w.geocode;

This can be worked around with, the following, but it is really a kludge.

WHERE
g.box_boundary @> box( w.geocode, w.geocode ) and
g.boundary @> w.geocode;

#2Bruce Momjian
bruce@momjian.us
In reply to: Paul Matthews (#1)
Re: BUG #4809: Missing Expected Operator

Paul Matthews wrote:

The following bug has been logged online:

Bug reference: 4809
Logged by: Paul Matthews
Email address: plm@netspace.net.au
PostgreSQL version: 8.3.7
Operating system: Linux OpenSuse 11.0
Description: Missing Expected Operator
Details:

Not a bug as such, but an obvious operator is missing.

WHERE
g.box_boundary @> w.geocode and
ERROR: operator does not exist: box @> point
g.boundary @> w.geocode;

This can be worked around with, the following, but it is really a kludge.

WHERE
g.box_boundary @> box( w.geocode, w.geocode ) and
g.boundary @> w.geocode;

This is already mentioned on the TODO list:

Add missing operators for geometric data types

Some geometric types do not have the full suite of geometric
operators, e.g. box @> point

--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +