[GRASS-dev] Re: [GRASS GIS] #385: description for v.db.reconnect.all

GRASS GIS trac at osgeo.org
Sun Nov 30 14:34:59 EST 2008


#385: description for v.db.reconnect.all
--------------------------+-------------------------------------------------
  Reporter:  nikos        |       Owner:  grass-dev at lists.osgeo.org
      Type:  enhancement  |      Status:  new                      
  Priority:  minor        |   Milestone:  6.4.0                    
 Component:  default      |     Version:  unspecified              
Resolution:               |    Keywords:                           
  Platform:  Unspecified  |         Cpu:  Unspecified              
--------------------------+-------------------------------------------------
Comment (by glynn):

 Replying to [comment:6 hamish]:

 > (if it belongs in the manual please move it into the manual instead of
 just deleting it)

 Done in r34639.

 > AFAICT Nikos's patch reduces to:
 {{{
 The name of '''old_database''' needs to be the exact string
 which appears as the fourth field printed by 'v.db.connect -g',
 i.e. with substituted variables.
 }}}

 > does that mean you need to use the full path not $MAPSET/... ?

 The script calls "v.db.connect -g" on each map, parses the output, and
 checks that the database field (4th column) is equal (by string
 comparison) to the old_database= value. If the database reported by the
 driver is a literal path, you need to use a literal path. If the database
 reported by the driver includes a trailing backslash, you need to include
 the trailing backslash, etc.

 The script can't realistically "normalise" the database name, as the
 format and semantics are driver-specific. For DBF, it's just a pathname;
 for a client-server DBMS, it can include all manner of connection
 parameters.

 If you feel that it's necessary to clarify this in the option description
 (rather than the manual), "as reported by v.db.connect" should suffice.

-- 
Ticket URL: <https://trac.osgeo.org/grass/ticket/385#comment:7>
GRASS GIS <http://grass.osgeo.org>


More information about the grass-dev mailing list