[postgis-devel] [PostGIS] #1026: && vs. &&& what's the difference

[PostGIS]

#1026: && vs. &&& what's the difference
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------
 These seem to be exactly the same in my installs shouldn't one be a 2d
 interacts check and the other a 3D interacts check?

 The definitions look the same and when testing they seem to give the same
 answers with 3D geometries even in cases where I expect &&& to return
 false and && to return true

 e.g. both have:

 {{{
 CREATE OPERATOR &&&(
   PROCEDURE = geometry_overlaps,
   LEFTARG = geometry,
   RIGHTARG = geometry,
   COMMUTATOR = &&&,
   RESTRICT = contsel,
   JOIN = contjoinsel);

 CREATE OPERATOR &&(
   PROCEDURE = geometry_overlaps,
   LEFTARG = geometry,
   RIGHTARG = geometry,
   COMMUTATOR = &&,
   RESTRICT = contsel,
   JOIN = contjoinsel);


 }}}

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1026>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.