[postgis-devel] [PostGIS] #835: ST_CollectionExtract returns EMPTY or NULL inconsistently

PostGIS trac at osgeo.org
Mon Jan 9 08:21:56 PST 2012


#835: ST_CollectionExtract returns EMPTY or NULL inconsistently
----------------------+-----------------------------------------------------
  Reporter:  strk     |       Owner:  pramsey      
      Type:  defect   |      Status:  closed       
  Priority:  medium   |   Milestone:  PostGIS 2.0.0
 Component:  postgis  |     Version:  trunk        
Resolution:  fixed    |    Keywords:               
----------------------+-----------------------------------------------------
Changes (by strk):

  * status:  new => closed
  * resolution:  => fixed


Comment:

 Ok, I've fixed liblwgeom to return typed EMPTIES in absence of matching
 types (r8717)
 But liblwgeom only wants COLLECTION input so can't do everything on
 itself.

 The wrapper I then fixed to always return NULL on type miss, no matter
 input
 (be it a complex multilevel collection or a simple empty, of any type).
 This is r8718.

 Note that I had to change an expected return in regress/regress.sql (test
 159) -- other existing tests were in tickets.sql and expected NULL for
 other kind of inputs.

 At least we're consistent now: NULL return when no matches are found.
 It's easy for me to get back on typed empty instead, if you scream loud
 enough.

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


More information about the postgis-devel mailing list