[GRASS-dev] no way to ID table columns outside of working mapset?
landa.martin at gmail.com
Mon Sep 8 12:51:01 EDT 2008
2008/9/8 Michael Barton <michael.barton at asu.edu>:
> v.info will probably do the trick.
> db.columns will return simply the columns without specifying the database
> and driver if it is for a vector whose connection is already set. Otherwise,
> it's not particularly easy to find out the database and driver for an
> attribute table connected to a vector that is not in the current working
> mapset because the commands will not accept a fully qualified name.
v.info is good candidate for this work, see menuform.py ...
Martin Landa <landa.martin gmail.com> * http://gama.fsv.cvut.cz/~landa *
More information about the grass-dev