Leo, congrats - you found a bug in db.dropcol :-) Fixed in CVS.
While doing that, I have also fixed the case that a "cat" column is already present in the original table (DBF file from a GRASS exported SHAPE file). Also in CVS (db.in.ogr). thanks, Markus Leonardo Lami wrote: > > The problem is that the new column is not conncted to a vector, infact: > > db.dropcol -f voti_province colum=cat > Forcing ... > WARNING: Deleting <cat> column which may be needed to keep table connected > to a vector map > ERROR: Column <cat> not found in table > > I don't know if I do something not correct... > > Thanks > leonardo > > > >> On Tue, Oct 23, 2007 at 10:04:12AM +0200, [EMAIL PROTECTED] wrote: >>> Hi all, >>> I'm testing the new databse commands on GRASS 6.3 cvs and I find a >>> problem >>> in db.in.ogr. >>> I'm using SQLite database, when I use db.in.ogr with a cvs or dbf table >>> Grass create the new table on .db SQLite file but it adds a first column >>> called "cat" that are not present in the original table. >> >> This is strange since the script contains >> >> # get rid of superfluous auto-added cat column >> db.dropcol --q -f $GIS_OPT_OUTPUT colum=cat >/dev/null 2>/dev/null >> >> (the cat column is added in the first place since v.in.ogr is >> used, then db.dropcol is called). >> >> It appears that db.dropcol fails. >> Try to run >> db.dropcol -f yourtable colum=cat >> >> This will show the error. >> >> Markus > -- View this message in context: http://www.nabble.com/db.in.ogr-and-v.db.join-tf4675839.html#a13372418 Sent from the Grass - Users mailing list archive at Nabble.com. _______________________________________________ grassuser mailing list grassuser@grass.itc.it http://grass.itc.it/mailman/listinfo/grassuser