[GRASS-dev] Re: [GRASS GIS] #809: v.db.addtable consistently fails
in winGrass
GRASS GIS
trac at osgeo.org
Fri Jan 8 06:24:03 EST 2010
#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:15 mmetz]:
> Right, and it should also be broken on Linux if there are
> whitespaces in the path name when manually connecting a table.
I just tested, it is.
> A mystery that no one discovered that yet...
I suspect they probably have, we've just never put all the pieces together
before. Especially Mac users who are more likely to see spaces in path
names.
> > suggestion: This is really a failure of the dbln file format.
> > In grass 7 change the dbln file format to use '|' as the field
> > sep. Include code in both the g7 and g6.5 the library functions
> > to quietly read either during the transition period.
...
> OK. And use G_tokenize() I assume.
in G_parser() is a G_tokenize() call which defines the sep as a two-
character array, which would be an easy way to temporarily allow either |
or " " as the sep.
> > You can't control what the map already has in it unless you
> > rebuild the map (which is perhaps not what you want). Another
> > plausible possibility is to add database= and driver= options
> > to v.db.addtable.
>
> Makes sense, and should not make the code too complicated.
> Something for g7?
or now or 6.4.1, if it is decided that inability to set a different DB for
new tables with v.db.addtable is actually a bug. (I guess you can already
adjust it to the desired value v.db.connect after creation, but that's a
bit ugly)
Hamish
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/809#comment:17>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list