[postgis-tickets] [PostGIS] #3031: "POINT EMPTY" as WKB defaults to "MULTIPOINT EMPTY" when restoring with copy and failing validation

[PostGIS]

#3031: "POINT EMPTY" as WKB defaults to "MULTIPOINT EMPTY" when restoring with
copy and failing validation
--------------------------------------------+-------------------------------
 Reporter:  jeanchristophesaville           |       Owner:  pramsey      
     Type:  defect                          |      Status:  new          
 Priority:  medium                          |   Milestone:  PostGIS 2.1.6
Component:  postgis                         |     Version:  2.1.x        
 Keywords:  POINT EMPTY , MULTIPOINT EMPTY  |  
--------------------------------------------+-------------------------------

Comment(by pramsey):

 OK, a patch for this at r13359. The patch is actually a suggestion from
 strk, to just allow MULTIPOINT EMPTY inputs a special pass through the
 typmod checker. It turned out to be less invasive code than I feared, so I
 went for that. The reason I did was to avoid emitting POINT(Nan nan) for
 our WKB output, which could potentially break downstream applications not
 expecting such a fun construct.

 Question: for trunk, do we go to POINT(nan nan) or keep our funny little
 hack in place?

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