[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 strk):

 Oh, now I got why for a multipoint we accept both multipoint and point. It
 is because the _value_ of POINT EMPTY becomes a multipoint and is thus
 accepted. So it's still the same exact problem we're trying to address.

 So, with the workaround fix in place, we should be accepting both points
 and multipoints (we only test empties) for the point case and we'd be
 still accepting both points and multipoints (empty) for the multipoint
 case. Basically it would be making the point typmod as "tolerant" as the
 multipoint one (when it comes to empties).

 The test should probably be further enhanced to also test non-empties...

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