[postgis-tickets] [PostGIS] #3470: ST_Polygonize doesn't accept NULL geometries

[PostGIS]

#3470: ST_Polygonize doesn't accept NULL geometries
----------------------+---------------------------------------
  Reporter:  kohnivo  |      Owner:  pramsey
      Type:  defect   |     Status:  new
  Priority:  low      |  Milestone:  PostGIS 2.2.3
 Component:  postgis  |    Version:  2.2.x
Resolution:           |   Keywords:  ST_Polygonize, NULL value
----------------------+---------------------------------------

Comment (by strk):

 For sure a dirty read fix needs backporting.
 But before backporting, should we also have a test with an array
 containing both null and not-null geometries ? Ideally we'd have the same
 behavior as ST_Collect (to be checked). There are two possible handling:
 the null elements are just skipped OR the whole array is considered null
 (and thus the output is also null)

--
Ticket URL: <https://trac.osgeo.org/postgis/ticket/3470#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.