[postgis-devel] [PostGIS] #666: ST_DumpPoints is not null safe

[PostGIS]

#666: ST_DumpPoints is not null safe
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 1.5.3
Component:  postgis  |     Version:  1.5.X        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by robe):

 I was wondering if it wouldn't be sufficient to just mark this function as
 STRICT like the way ST_Dump is marked.  Do people think its necessary to
 even put logic about NULL handling in the function if the function is
 marked as strict.

 Even though this is an SQL function, I don't see any benefit of keeping it
 non-strict since it could never utilize spatial indexes anyway.

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