[GRASS-dev] [GRASS GIS] #2569: Allow v.db.reconnect.all to handle database errors more graciously

[GRASS GIS]

#2569: Allow v.db.reconnect.all to handle database errors more graciously
-------------------------+--------------------------------------------------
 Reporter:  ewcgrass     |       Owner:  grass-dev@…              
     Type:  enhancement  |      Status:  new                      
 Priority:  normal       |   Milestone:  7.1.0                    
Component:  Database     |     Version:  unspecified              
 Keywords:               |    Platform:  Linux                    
      Cpu:  x86-64       |  
-------------------------+--------------------------------------------------
 v.db.reconnect.all appears to stop at every database error it encounters
 during migration of database tables from .dbf to sqlite (and likely others
 too). While this provides a great opportunity to clean up incorrect
 database tables, it destroys work flow.

 It would be nice if flags could be added to allow v.db.reconnect.all to
 skip errors and list them, while continuing to process the rest of the
 database tables in the mapset. Then those tables which caused the errors
 could be more easily audited and repaired.

 This would be extremely useful for the numerous vector file migrations
 that are necessary from GRASS 6.x to 7.0, but it may be too late to
 incorporate it into version 7.0 at this time, which is why I suggest it as
 something for version 7.1 or later.

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/2569>
GRASS GIS <http://grass.osgeo.org>