[postgis-tickets] [PostGIS] #1024: Change 3D relationship functions to use &&& instead of &&

[PostGIS]

#1024: Change 3D relationship functions to use &&& instead of &&
-------------------------+--------------------------------------------------
 Reporter:  robe         |       Owner:  pramsey      
     Type:  enhancement  |      Status:  new          
 Priority:  high         |   Milestone:  PostGIS 2.2.0
Component:  postgis      |     Version:  trunk        
 Keywords:               |  
-------------------------+--------------------------------------------------
Changes (by robe):

  * priority:  medium => high
  * type:  task => enhancement


Comment:

 Okay we really need this.  If I have a nd_index, by ST_3DIntersects does
 not use an index.

 I had to change to


 {{{
 CREATE OR REPLACE FUNCTION st_3dintersects(
     geom1 geometry,
     geom2 geometry)
   RETURNS boolean AS
 'SELECT $1 &&& $2 AND $1 && $2 AND _ST_3DIntersects($1, $2)'
   LANGUAGE sql IMMUTABLE
   COST 100;
 }}}


 rather than instead of, I think we need both.  I had thought that && would
 use the 3D index but it doesn't.  So we need both in case someone has only
 a 2D index in place so that the function can use a 3D or 2D index.

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/1024#comment:15>
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.