[GRASS-user] bug in v.db.renamecol

GRASS GRASS user
1

Hello all,
I found a small bug in v.db.renamecol

working on dbf- database driver, renaming a column, if (like I made) you try to use a column name greater than 10 characters length, then it gives an error warning, and creates a column with the new name (cut at the end to fit 10 char), but does not fill in the column values, and(!) deletes the old column.
This is: column data is lost!

Cheers
Manuel

--

_______________________________________________________________________
Dr. Manuel Seeger
Wiss. Assistent Scientific Assistant
Physische Geographie Dpt. of Physical Geography
FB VI - Geographie/Geowissenschaften Geography/Geosciences
Universität Trier University of Trier
D - 54286 Trier
Tel.: +49-651-201 4557
Fax: +49-651-201 3976
Web: http://www-neu.uni-trier.de/index.php?id=9607

2

On Feb 7, 2008 4:47 PM, Dr. Manuel Seeger <seeger@uni-trier.de> wrote:

Hello all,
I found a small bug in v.db.renamecol

working on dbf- database driver, renaming a column, if (like I made) you
try to use a column name greater than 10 characters length, then it
gives an error warning, and creates a column with the new name (cut at
the end to fit 10 char), but does not fill in the column values, and(!)
deletes the old column.
This is: column data is lost!

That's bad! Fixed:

v.db.renamecol myarchsites co=str1,abcdefghijk
ERROR: Column name too long <abcdefghijk>: the DBF driver only supports up
       to 10 characters as column name.

http://trac.osgeo.org/grass/changeset/30007

(also fixed in 6.3 rel.branch).

markus