[postgis-devel] [PostGIS] #536: Get rid of the STRICT on geography ST_Intersects

[PostGIS]

#536: Get rid of the STRICT on geography ST_Intersects
----------------------+-----------------------------------------------------
  Reporter:  robe     |       Owner:  pramsey      
      Type:  defect   |      Status:  new          
  Priority:  high     |   Milestone:  PostGIS 1.5.2
 Component:  postgis  |     Version:  1.5.X        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by robe):

 Because we don't have STRICT on them.
 The geometry one looks like this


 {{{
 CREATE OR REPLACE FUNCTION st_intersects(geometry, geometry)
   RETURNS boolean AS
 'SELECT $1 && $2 AND _ST_Intersects($1,$2)'
   LANGUAGE 'sql' IMMUTABLE
 }}}

 This new affection for STRICT started recently -- perhaps becuase of our
 whole NULL IS NULL = NULL NULL NULL = false philosophizing :)

 Actually geography ST_Dwithin is fine -- doesn't have strict.  I suspect
 that is why I never noticed it because I rarely use ST_Intersects for my
 proximity queries since I usually need buffer regions.

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