Markus Neteler wrote: > >> > (Hopefully) fixed in 6.4.develbranch and 7.trunk. > >> > >> Do I understand correctly that the patch ignores the column if the name > >> already exists ? Wouldn't it be more "user-friendly" to rename it ? > > > > I don't know about "user-friendly", but it would be safer to just > > abort with an error if the column already exists. > > > > If you're going to replace the contents of an existing column, you > > should only do so if --overwrite is given. > > Sounds reasonable. > It would be good if someone adds both error abort and --overwrite > flag in that script.
AIUI, you already have the error abort for free, due to v.db.addcol failing. Handling --overwrite would be nice, but in the meantime the main thing is not to try to circumvent the error by unconditionally deleting the column. So, I have reverted your recent change. -- Glynn Clements <[EMAIL PROTECTED]> _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
