[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
----------------------+---------------------------------------
Changes (by dbaston):

 * milestone:   => PostGIS 2.2.3


Comment:

 I've fixed this in trunk at r14882.

 Should this be backported to 2.2?  It ''does'' change behavior, but it
 looks like the old behavior involves a dirty read, based on the error
 messages kohnivo is reporting, as well as what I'm seeing:

 {{{
 postgres=# SELECT '#3470',
 ST_Polygonize(ARRAY[NULL::geometry]::geometry[]);
 ERROR:  Unknown geometry type: 64 - Invalid type
 postgres=# SELECT '#3470', ST_Polygonize(ARRAY['LINESTRING (0 0, 1 1)',
 NULL::geometry]::geometry[]);
 ERROR:  Unknown geometry type: 17337632 - Invalid type
 postgres=# SELECT '#3470', ST_Polygonize(ARRAY['LINESTRING (0 0, 1 1)',
 NULL]::geometry[]);
 ERROR:  Unknown geometry type: 0 - Unknown
 }}}

 Porting it back to 2.1 is trickier, as the fix involves switching to
 simplified code introduced in 2.2.

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