Menu

#113 Postgres/PostGIS and && operators

open-accepted
General (45)
5
2004-12-01
2004-11-30
No

This isn't really a bug, per se, so you might classify
this as a feature request.

I'm trying to use the PostGIS operators for bounding
box operations. The "&" operator is also used by JDBC
as a positional parameter and iSQL-Viewer prompts for a
value. These two conflict, unfortunately. Would it be
possible to *NOT* prompt for a value for the following
operators:
&<
&>
&&

I've used the "@" operator and it seems to work
alright, as do "<<", ">>", "~", and "~=". The only
ones that seem to pose a problem are the & related
operators, presumably because that's the standard way
of denoting replaceable parameters.

FWIW, here's my query:
SELECT a.*
FROM tbl_poi a, public.tbl_current_user_location b
WHERE
a.latlon && Expand(b.latlon,1)
AND
Distance(b.latlon,a.latlon) < 1;

This works if I cut/paste it into pgsql directly.

This isn't a show stopper, but it would help :-).
Excellent work on the tool!! :-)

Rgds,

Bret

Discussion

  • Markus A. Kobold

    • status: open --> open-accepted
     
  • Markus A. Kobold

    Logged In: YES
    user_id=67341

    This Bug has been Accepted and will befurhter investigated for a
    better solution.

    Thank you for your support.

     
  • Markus A. Kobold

    Logged In: YES
    user_id=67341

    Update has been posted to CVS tree update will also be available
    upon the next release.

     

Log in to post a comment.

MongoDB Logo MongoDB