[GRASS-dev] Re: [GRASS GIS] #809: v.db.addtable consistently fails in winGrass

[GRASS GIS]

#809: v.db.addtable consistently fails in winGrass
------------------------------+---------------------------------------------
  Reporter:  JonBall          |       Owner:  grass-dev at lists.osgeo.org
      Type:  defect           |      Status:  new                      
  Priority:  critical         |   Milestone:  6.4.0                    
 Component:  Vector           |     Version:  svn-releasebranch64      
Resolution:                   |    Keywords:  v.db.addtable, wingrass  
  Platform:  MSWindows Vista  |         Cpu:  x86-64                   
------------------------------+---------------------------------------------
Comment (by hamish):

 Replying to [comment:18 mmetz]:
 > Replying to [comment:16 hamish]:
 > > I've just attached to this ticket a patch against 6.5 which
 > > allows spaces in pathnames
 ...
 > Tested, works fine.

 committed in 6.5svn and trunk.

 > One minor bug though: in the new v.db.addtable line 129
 [g.findfile]
 > does not work with a fully qualified name,

 interestingly it pretty much works if you just chop off the @mapset
 part because g.findfile searches the full mapset path as a module would.

 Anyway, I've ripped this code out now in favor of using the VAR file's
 default DB settings for the mapset. So you are able to now control it
 instead of being locked to what the map was already using. Committed in
 6.5svn and trunk.



 > For grass7, I would suggest to use fs="|" as default
 > (anything but whitespace) whenever dblinks are written or
 > printed, e.g. Vect_write_dblinks() and v.db.connect -p

 Done and done. I'm sure we'll hear about it if there are any problems, but
 after some light testing it seems to work ok.


 the only thing left to decide is when to backport this stuff to 6.4.


 Hamish

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