[GRASS-user] DB copy for v.db.connect

Glynn Clements glynn at gclements.plus.com
Mon Nov 3 14:58:51 EST 2008


Moritz Lennert wrote:

> > it is advised to copy DB before running v.db.connect to a second map, as
> > if you delete the second map the DB will be removed for the parent map
> > too.  db.copy seems the obvious way to do that, but db.* only work if the
> > source map (ie table) is in the same mapset as the new map.  
> 
> ???
> 
> db.copy doesn't care about maps (only v.db.* modules care about maps),
> it only cares about tables, databases and drivers and AFAIK you can copy
> any table from any supported database to any other supported database...

Right. Although with DBF, the default database is the current mapset's
"dbf" directory. This just means that you have to explicitly specify
the database rather than using the default.

-- 
Glynn Clements <glynn at gclements.plus.com>


More information about the grass-user mailing list