Subject: v.db.droptable: an 'ERROR' is always issued though the command completes OK
Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 2006-09-08
Although v.db.droptable works as expected and removes the reqested table, it always issues an 'ERROR' in the end, which is not good - the user *will* think something went wrong indeed.
Example:
$ v.db.droptable map=ditches layer=1 Removing following table name connected to selected layer: ditches
Removing table <ditches> linked to layer <1> of vector map <ditches>
Are you sure (y/n)? [n]
y
Dropping table <ditches>...
Current attribute table link(s):
ERROR: Database connection for map <ditches> is not defined in DB file
Maciek
-------------------------------------------- Managed by Request Tracker
Subject: v.db.droptable: an 'ERROR' is always issued though the
command completes OK
..
Although v.db.droptable works as expected and removes the reqested
table, it always issues an 'ERROR' in the end, which is not good - the
user *will* think something went wrong indeed.
Example:
$ v.db.droptable map=ditches layer=1 Removing following table name
connected to selected layer: ditches Removing table <ditches> linked
to layer <1> of vector map <ditches> Are you sure (y/n)? [n]
y
Dropping table <ditches>...
Current attribute table link(s):
ERROR: Database connection for map <ditches> is not defined in DB file
I've added a line to the script in CVS to make the error message more
instructive.
I can't send the "ERROR:" message to /dev/null as "v.db.connect -p"
sends its output to stderr. This should probably be changed to stdout.