[postgis-devel] [PostGIS] #198: shp2pgsql gives bad output on bad input

[PostGIS]

#198: shp2pgsql gives bad output on bad input
----------------------+-----------------------------------------------------
  Reporter:  pramsey  |       Owner:  mcayland     
      Type:  defect   |      Status:  new          
  Priority:  medium   |   Milestone:  postgis 1.4.0
 Component:  postgis  |     Version:  trunk        
Resolution:           |    Keywords:               
----------------------+-----------------------------------------------------
Comment (by robe):

 +1 Yes I concur - we should not be doing validity checking on load unless
 we provide a switch to turn it on.  This is really something that deserves
 a switch.

 Before you could ignore bad records by removing the begin/commits - am I
 correct in saying that is not an option any more as the .sql generation
 will just choke?

-- 
Ticket URL: <http://trac.osgeo.org/postgis/ticket/198#comment:3>
PostGIS <http://trac.osgeo.org/postgis/>
PostGIS