[postgis-devel] [PostGIS] #700: ST_Boundary collection of empties crashes

[PostGIS]

#700: ST_Boundary collection of empties crashes
---------------------+------------------------------------------------------
 Reporter:  robe     |       Owner:  pramsey      
     Type:  defect   |      Status:  new          
 Priority:  medium   |   Milestone:  PostGIS 2.0.0
Component:  postgis  |     Version:  trunk        
 Keywords:           |  
---------------------+------------------------------------------------------

Comment(by pramsey):

 Yes, probably too early. Maybe you can come to the sprint and we can talk
 it out? The issue then becomes the definition of "empty". Right now
 lwgeom_is_empty() has a particular definition (has zero sub-elements)
 which is useful on some cases (if you want to extract the n-the element of
 a collection of empty things you still can) but not in others (like this
 ticket). Perhaps I just need two definitions ("has zero subelements" and
 "has no spatial definition") to apply in different cases. But it's an
 annoying conundrum, and a bit of a waste of time until we get the core
 functionality in place again on new foundations.

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