v.db.addcol renamed to v.db.addcolumn

git-svn-id: https://svn.osgeo.org/grass/grass/trunk@39817 15284696-431f-4ddb-bdfa-cd5b030d7da7

display/d.vect/d.vect.html

@@ -35,9 +35,9 @@ cat|label|GRASSRGB
 190|TENNA|123:45:67
 </pre></div>
 <P>
-To add the GRASSRGB color column, use <em>v.db.addcol</em>:
+To add the GRASSRGB color column, use <em>v.db.addcolumn</em>:
 <div class="code"><pre>
-v.db.addcol testisola col="GRASSRGB varchar(11)"
+v.db.addcolumn testisola col="GRASSRGB varchar(11)"
 </pre></div>
 <P>
 To add/change a color, use <em>v.db.update</em>:
@@ -94,7 +94,7 @@ d.vect -z random3d_del type=area zcol=gyr
 <a HREF="d.what.vect.html">d.what.vect</a>,
 <a HREF="d.rast.html">d.rast</a>,
 <a HREF="v.colors.html">v.colors</a>,
-<a HREF="v.db.addcol.html">v.db.addcol</a>,
+<a HREF="v.db.addcolumn.html">v.db.addcolumn</a>,
 <a HREF="v.db.update.html">v.db.update</a><br>
 <a HREF="sql.html">GRASS SQL interface</a>
 </em>

gui/wxpython/docs/wxGUI.Attribute_Table_Manager.html

@@ -28,7 +28,7 @@
 
 <p>
 <em>
-  <a href="v.db.addcol.html">v.db.addcol</a>,
+  <a href="v.db.addcolumn.html">v.db.addcolumn</a>,
   <a href="v.db.connect.html">v.db.connect</a>,
   <a href="v.db.dropcolumn.html">v.db.dropcolumn</a>,
   <a href="v.db.renamecolumn.html">v.db.renamecolumn</a>,

gui/wxpython/gui_modules/dbm.py

@@ -1660,10 +1660,10 @@ class AttributeManager(wx.Frame):
         list.SetStringItem(index, 1, str(type))
         list.SetStringItem(index, 2, str(length))
         
-        # add v.db.addcol command to the list
+        # add v.db.addcolumn command to the list
         if type == 'varchar':
             type += ' (%d)' % length
-        self.listOfCommands.append(('v.db.addcol',
+        self.listOfCommands.append(('v.db.addcolumn',
                                     { 'map' : self.vectorName,
                                       'layer' : self.layer,
                                       'columns' : '%s %s' % (name, type) }
@@ -1740,7 +1740,7 @@ class AttributeManager(wx.Frame):
 
     def ApplyCommands(self):
         """!Apply changes"""
-        # perform GRASS commands (e.g. v.db.addcol)
+        # perform GRASS commands (e.g. v.db.addcolumn)
         if len(self.listOfCommands) > 0:
             for cmd in self.listOfCommands:
                 gcmd.RunCommand(prog = cmd[0],

lib/db/sqlp/sql.html

@@ -107,7 +107,7 @@ v.db.select mysites where="id LIKE 'P%'"
 
 <p><b>Example</b> of null handling:
 <div class="code"><pre>
-v.db.addcol map=roads col="nulltest int"
+v.db.addcolumn map=roads col="nulltest int"
 v.db.update map=roads col=nulltest value=1 where="cat &gt; 2"
 d.vect roads where="nulltest is null"
 v.db.update map=roads col=nulltest value=2 where="cat &lt;= 2"
@@ -116,7 +116,7 @@ v.db.update map=roads col=nulltest value=2 where="cat &lt;= 2"
 
 <p><b>Examples</b> of complex expressions in updates (using v.db.* modules):
 <div class="code"><pre>
-v.db.addcol map=roads col="exprtest double precision"
+v.db.addcolumn map=roads col="exprtest double precision"
 v.db.update map=roads col=exprtest value=cat/nulltest
 v.db.update map=roads col=exprtest value=cat/nulltest+cat where=cat=1
 </pre></div>
@@ -146,7 +146,7 @@ d.vect roads where="cat&gt;exprtest"
 # North Carolina data set: convert string column to double precision
 #  copy map into current mapset
 g.copy vect=geodetic_pts,mygeodetic_pts
-v.db.addcol mygeodetic_pts col="zval double precision"
+v.db.addcolumn mygeodetic_pts col="zval double precision"
 
 # the 'z_value' col contains 'N/A' strings, not to be converted
 v.db.update mygeodetic_pts col=zval \

scripts/v.colors/v.colors.html

@@ -83,7 +83,7 @@ d.vect -a tin
 <A HREF="r.colors.html">r.colors</A><BR>
 <A HREF="r.colors.stddev.html">r.colors.stddev</A><BR>
 <A HREF="r.what.color.html">r.what.color</A><BR>
-<A HREF="v.db.addcol">v.db.addcol</A><BR>
+<A HREF="v.db.addcolumn">v.db.addcolumn</A><BR>
 <A HREF="v.db.select.html">v.db.select</A><BR>
 <A HREF="db.execute.html">db.execute</A>
 </EM>

scripts/v.colors/v.colors.py

@@ -192,7 +192,7 @@ def main():
     if rgb_column not in cols:
         # RGB Column not found, create it
 	grass.message(_("Creating column <%s> ...") % rgb_column)
-	if 0 != grass.run_command('v.db.addcol', map = map, layer = layer, column = "%s varchar(11)" % rgb_column):
+	if 0 != grass.run_command('v.db.addcolumn', map = map, layer = layer, column = "%s varchar(11)" % rgb_column):
 	    grass.fatal(_("Creating color column"))
     else:
 	column_type = cols[rgb_column]

scripts/v.db.addcolumn/v.db.addcol.html

@@ -1,12 +1,12 @@
 <h2>DESCRIPTION</h2>
 
-<em>v.db.addcol</em> adds one or more column(s) to the attribute table
+<em>v.db.addcolumn</em> adds one or more column(s) to the attribute table
 connected to a given vector map. It automatically checks the connection for the
 specified layer.
 
 <h2>NOTES</h2>
 
-v.db.addcol is a front-end to <em>db.execute</em> to allow easier usage.
+v.db.addcolumn is a front-end to <em>db.execute</em> to allow easier usage.
 
 The supported types of columns depend on the database backend. However, all
 backends should support VARCHAR, INT, DOUBLE PRECISION and DATE. The default
@@ -18,14 +18,14 @@ The existing database connection(s) can be verified with <em>v.db.connect</em>.
 
 Adding a single column:<br>
 <div class="code"><pre>
-v.db.addcol sentiero_brenta_points columns="slope double precision"
+v.db.addcolumn sentiero_brenta_points columns="slope double precision"
 v.info -c sentiero_brenta_points
 </pre></div>
 
 <p>
 Adding two columns:<br>
 <div class="code"><pre>
-v.db.addcol sentiero_brenta_points columns="slope double precision,myname varchar(15)"
+v.db.addcolumn sentiero_brenta_points columns="slope double precision,myname varchar(15)"
 v.info -c sentiero_brenta_points
 </pre></div>
 

scripts/v.db.addcolumn/v.db.addcol.py

@@ -2,7 +2,7 @@
 #
 ############################################################################
 #
-# MODULE:       v.db.addcolumn
+# MODULE:       v.db.addcolumnumn
 # AUTHOR(S):   	Moritz Lennert 
 #               Converted to Python by Glynn Clements
 # PURPOSE:      interface to db.execute to add a column to the attribute table

scripts/v.db.addtable/v.db.addtable.html

@@ -46,7 +46,7 @@ v.info -c sentiero_brenta_points
 <em><a HREF="db.droptable.html">db.droptable</a></em>,
 <em><a HREF="db.execute.html">db.execute</a></em>,
 <em><a HREF="v.category.html">v.category</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
 <em><a HREF="v.db.connect.html">v.db.connect</a></em>,
 <em><a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,
 <em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,

scripts/v.db.dropcolumn/v.db.dropcolumn.html

@@ -23,7 +23,7 @@ v.info -c sentiero_brenta_points
 
 <em><a HREF="db.droptable.html">db.droptable</a></em>,
 <em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
 <em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
 <em><a HREF="v.db.connect.html">v.db.connect</a></em>,
 <em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,

scripts/v.db.dropcolumn/v.db.dropcolumn.py

@@ -7,7 +7,7 @@
 #               Converted to Python by Glynn Clements
 # PURPOSE:      interface to db.execute to drop a column from the 
 #               attribute table connected to a given vector map
-#               - Based on v.db.addcol
+#               - Based on v.db.addcolumn
 #               - with special trick for SQLite
 # COPYRIGHT:    (C) 2007 by the GRASS Development Team
 #

scripts/v.db.droprow/v.db.droprow.html

@@ -37,7 +37,7 @@ v.univar rand5k_elev_filt type=point column=elevation
 
 <em><a HREF="db.droptable.html">db.droptable</a></em>,
 <em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
 <em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
 <em><a HREF="v.db.connect.html">v.db.connect</a></em>,
 <em><a HREF="v.db.dropcol.html">v.db.dropcol</a></em>,

scripts/v.db.droptable/v.db.droptable.html

@@ -22,7 +22,7 @@ v.db.connect -p sentiero_brenta_points
 
 <em><a HREF="db.droptable.html">db.droptable</a></em>,
 <em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
 <em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
 <em><a HREF="v.db.connect.html">v.db.connect</a></em>,
 <em><a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,

scripts/v.db.join/v.db.join.py

@@ -106,7 +106,7 @@ def main():
 	    coltype = "%s" % col[1]
 	colspec = "%s %s" % (colname, coltype)
 
-	if grass.run_command('v.db.addcol', map = map, columns = colspec, layer = layer) != 0:
+	if grass.run_command('v.db.addcolumn', map = map, columns = colspec, layer = layer) != 0:
 	    grass.fatal(_("Error creating column <%s>.") % colname)
 
 	stmt = template.substitute(table = maptable, column = column,

scripts/v.db.renamecolumn/v.db.renamecolumn.html

@@ -34,7 +34,7 @@ v.info -c myroads
 <h2>SEE ALSO</h2>
 
 <em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
 <em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
 <em><a HREF="v.db.connect.html">v.db.connect</a></em>,
 <em><a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a></em>,

scripts/v.db.renamecolumn/v.db.renamecolumn.py

@@ -104,7 +104,7 @@ def main():
 	else:
 	    colspec = "%s %s" % (newcol, oldcoltype)
 
-	grass.run_command('v.db.addcol', map = map, layer = layer, column = colspec)
+	grass.run_command('v.db.addcolumn', map = map, layer = layer, column = colspec)
 	sql = "UPDATE %s SET %s=%s" % (table, newcol, oldcol)
 	grass.write_command('db.execute', input = '-', database = database, driver = driver, stdin = sql)
 	grass.run_command('v.db.dropcolumn', map = map, layer = layer, column = oldcol)

scripts/v.db.update/v.db.update.html

@@ -14,7 +14,7 @@ For complex SQL UPDATE statements, <em>db.execute</em> should be used.
 Spearfish: adding new column, inserting selectively a specified value:
 <div class="code"><pre>
 g.copy vect=fields,myfields
-v.db.addcol myfields col="polynum integer"
+v.db.addcolumn myfields col="polynum integer"
 v.db.update myfields col=polynum val=42 where="label='V. White#1'"
 v.db.select myfields
 </pre></div>
@@ -24,7 +24,7 @@ Spearfish: adding new column, copying values from other table column with
 on the fly calculation:
 <div class="code"><pre>
 g.copy vect=fields,myfields
-v.db.addcol myfields col="polynum integer"
+v.db.addcolumn myfields col="polynum integer"
 v.db.update myfields col=polynum qcol="cat*2"
 v.db.select myfields
 </pre></div>
@@ -39,7 +39,7 @@ v.db.update mygeodetic_pts col=zval qcol="CAST(z_value AS double precision)" \
 <h2>SEE ALSO</h2>
 
 <em><a HREF="db.execute.html">db.execute</a></em>,
-<em><a HREF="v.db.addcol.html">v.db.addcol</a></em>,
+<em><a HREF="v.db.addcolumn.html">v.db.addcolumn</a></em>,
 <em><a HREF="v.db.addtable.html">v.db.addtable</a></em>,
 <em><a HREF="v.db.connect.html">v.db.connect</a></em>,
 <em><a HREF="v.db.droptable.html">v.db.droptable</a></em>,

scripts/v.rast.stats/v.rast.stats.py

@@ -207,7 +207,7 @@ def main():
 
     if addcols:
 	grass.verbose("Adding columns <%s>" % addcols)
-	if grass.run_command('v.db.addcol', map = vector, columns = addcols) != 0:
+	if grass.run_command('v.db.addcolumn', map = vector, columns = addcols) != 0:
 	    grass.fatal(_("Cannot continue (problem adding columns)."))
 
     #loop over cats and calculate statistics:

scripts/v.what.vect/v.what.vect.html

@@ -7,7 +7,7 @@ attribute table into the attribute table of <u>points</u> present in the
 <h2>NOTES</h2>
 
 The upload <b>column</b>, into which the query results are stored, must be
-present in the <b>vector</b> map. Use <em>v.db.addcol</em> to add one if needed.
+present in the <b>vector</b> map. Use <em>v.db.addcolumn</em> to add one if needed.
 <p>
 Use dmax parameter to control query distance tolerance (how far points can be from 
 <b>qvector</b> features). For more options, use
@@ -26,7 +26,7 @@ map at points' locations:
 
 <div class="code"><pre>
 g.copy vect=archsites,myarchsites
-v.db.addcol myarchsites col="owner varchar(25)"
+v.db.addcolumn myarchsites col="owner varchar(25)"
 v.what.vect myarchsites qvect=fields column=owner qcolumn=label
 # verification:
 v.db.select myarchsites
@@ -36,7 +36,7 @@ v.db.select myarchsites
 <h2>SEE ALSO</h2>
 
 <em>
-<a HREF="v.db.addcol.html">v.db.addcol</a>,
+<a HREF="v.db.addcolumn.html">v.db.addcolumn</a>,
 <a HREF="v.db.select.html">v.db.select</a>,
 <a HREF="v.distance.html">v.distance</a>,
 <a HREF="v.rast.stats.html">v.rast.stats</a>,

vector/v.db.connect/v.db.connect.html

@@ -195,7 +195,7 @@ v.db.connect map=mytable driver=pg database="host=localhost,dbname=meteo" \
 <a HREF="db.tables.html">db.tables</a>,
 <a HREF="v.db.addtable.html">v.db.addtable</a>,
 <a HREF="v.db.droptable.html">v.db.droptable</a>,
-<a HREF="v.db.addcol.html">v.db.addcol</a>,
+<a HREF="v.db.addcolumn.html">v.db.addcolumn</a>,
 <a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a>,
 <a HREF="v.external.html">v.external</a>,
 <a HREF="v.in.db.html">v.in.db</a>,

vector/v.distance/v.distance.html

@@ -15,7 +15,7 @@ that if a point is in an island (area WITHOUT category), <EM>v.distance</EM>
 does not search for the nearest area WITH category; the island is identified 
 as the nearest and category updated to null.
 <p>
-The upload <em>column</em>(s) must already exist. Create one with <em>v.db.addcol</em>.
+The upload <em>column</em>(s) must already exist. Create one with <em>v.db.addcolumn</em>.
 <p>
 In lat-long locations <em>v.distance</em> gives distances (<em>dist</em>
 and <em>to_along</em>) in meters not in degrees calculated as geodesic
@@ -101,7 +101,7 @@ upload=cat,dist column=nearest_id,dist_to_nr</tt>.
 g.copy vect=bugsites,bugs
 
 # add new attribute column to hold nearest archsite category number
-v.db.addcol map=bugs column="nrst_arch INTEGER"
+v.db.addcolumn map=bugs column="nrst_arch INTEGER"
 
 v.distance from=bugs to=archsites to_type=point upload=to_attr \
   to_column=cat column=nrst_arch out=vdistance_vectors_raw
@@ -131,7 +131,7 @@ given upload option.
 
 <EM>
 <a href="r.distance.html">r.distance</a>,
-<a href="v.db.addcol.html">v.db.addcol</a>,
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
 <a href="v.what.vect.html">v.what.vect</a>
 </EM>
 

vector/v.net.path/v.net.path.html

@@ -63,7 +63,7 @@ Shortest path from two digitized nodes (Spearfish):
 
 <div class="code"><pre>
 g.copy vect=roads,myroads
-v.db.addcol myroads col="forward double precision, backward double precision"
+v.db.addcolumn myroads col="forward double precision, backward double precision"
 
 # define traveling costs as inverse of speed limit:
 v.db.update myroads col=forward val=1/50

vector/v.net.salesman/v.net.salesman.html

@@ -9,7 +9,7 @@ Traveling salesman for 6 digitized nodes (Spearfish):
 
 <div class="code"><pre>
 g.copy vect=roads,myroads
-v.db.addcol myroads col="cost double precision"
+v.db.addcolumn myroads col="cost double precision"
 
 # define traveling costs as inverse of speed limit:
 v.db.update myroads col=cost val=1/50

vector/v.net.steiner/v.net.steiner.html

@@ -17,7 +17,7 @@ Steiner tree for for 6 digitized nodes (Spearfish):
 
 <div class="code"><pre>
 g.copy vect=roads,myroads
-v.db.addcol myroads col="cost double precision"
+v.db.addcolumn myroads col="cost double precision"
 
 # define traveling costs as inverse of speed limit:
 v.db.update myroads col=cost val=1/50

vector/v.to.3d/description.html

@@ -20,7 +20,7 @@ NULL values are silently converted to height 0.0.
 
 <div class="code"><pre>
 # convert z-values from string to double
-v.db.addcol map=geodetic_pts columns="Z_VALUE_D double precision"
+v.db.addcolumn map=geodetic_pts columns="Z_VALUE_D double precision"
 v.db.update map=geodetic_pts column=Z_VALUE_D qcolumn=Z_VALUE
 v.db.select map=geodetic_pts columns=cat,Z_VALUE,Z_VALUE_
 

vector/v.to.3d/v.to.3d.html

@@ -20,7 +20,7 @@ NULL values are silently converted to height 0.0.
 
 <div class="code"><pre>
 # convert z-values from string to double
-v.db.addcol map=geodetic_pts columns="Z_VALUE_D double precision"
+v.db.addcolumn map=geodetic_pts columns="Z_VALUE_D double precision"
 v.db.update map=geodetic_pts column=Z_VALUE_D qcolumn=Z_VALUE
 v.db.select map=geodetic_pts columns=cat,Z_VALUE,Z_VALUE_
 

vector/v.to.db/v.to.db.html

@@ -41,7 +41,7 @@ needed.
 Updating the table has to be done column-wise. The <em>column</em> must be
 present in the table, except when using the <b>print only</b> (<b>-p</b>)
 mode. Use <em><a href="db.execute.html">db.execute</a></em> or
-<em><a href="v.db.addcol.html">v.db.addcol</a></em> to add new columns if
+<em><a href="v.db.addcolumn.html">v.db.addcolumn</a></em> to add new columns if
 needed.
 
 <H2>EXAMPLES</H2>
@@ -82,7 +82,7 @@ v.to.db map=pointsmap option=coor col=x,y,z
 Transfer attributes from a character column (with numeric contents) to a new
 integer column:<br>
 <div class="code"><pre>
-v.db.addcol usa_income_employment2002 col="FIPS_NUM integer"
+v.db.addcolumn usa_income_employment2002 col="FIPS_NUM integer"
 v.to.db usa_income_employment2002 option=query col=FIPS_NUM qcol=STATE_FIPS
 </pre></div>
 
@@ -108,7 +108,7 @@ D = 2 * (log perimeter) / (log area):<br>
 </tt>
 <div class="code"><pre>
 g.copy vect=soils,mysoils
-v.db.addcol mysoils col="d double precision"
+v.db.addcolumn mysoils col="d double precision"
 v.to.db mysoils option=fd column="d"
 
 g.region vect=mysoils res=50
@@ -159,7 +159,7 @@ v.to.db -p roads option=count type=line
 <a href="db.execute.html">db.execute</a>,
 <a href="v.category.html">v.category</a>,
 <a href="v.db.addtable.html">v.db.addtable</a>,
-<a href="v.db.addcol.html">v.db.addcol</a>,
+<a href="v.db.addcolumn.html">v.db.addcolumn</a>,
 <a href="v.db.connect.html">v.db.connect</a>,
 <a href="v.distance.html">v.distance</a>,
 <a href="v.report.html">v.report</a>,

vector/v.transform/v.transform.html

@@ -88,7 +88,7 @@ Spearfish example with automated elevation extraction for vertical shift:
 # work on own map copy:
 g.copy vect=archsites@PERMANENT,myarchsites
 # add new 'zs' column to later store height of each site:
-v.db.addcol myarchsites col="zs double precision"
+v.db.addcolumn myarchsites col="zs double precision"
 
 # set region to elevation map and fetch individual heights:
 g.region rast=elevation.10m -p

vector/v.vol.rst/v.vol.rst.html

@@ -76,7 +76,7 @@ g.region res=50 tbres=50 b=0 t=1500 -ap3
 r.random elevation.10m vector_output=elevrand n=200
 
 # conversion to 3D
-v.db.addcol elevrand col="x double precision, y double precision"
+v.db.addcolumn elevrand col="x double precision, y double precision"
 v.to.db elevrand option=coor col=x,y
 v.db.select elevrand
 
@@ -94,7 +94,7 @@ v.db.dropcolumn elevrand_3d col=value
 # (Soil range types taken from the USDA Soil Survey)
 d.rast soils.range
 d.vect elevrand_3d
-v.db.addcol elevrand_3d col="soilrange integer"
+v.db.addcolumn elevrand_3d col="soilrange integer"
 v.what.rast elevrand_3d col=soilrange rast=soils.range
 
 # fix 0 (no data in raster map) to NULL:

vector/v.voronoi/v.voronoi.html

@@ -24,7 +24,7 @@ and both (right pane)</i>
 
 Voronoi diagrams may be used for nearest-neighbor flood filling.
 Give the centroids attributes (start with
-<em><A HREF="v.db.addcol.html">v.db.addcol</A></em>),
+<em><A HREF="v.db.addcolumn.html">v.db.addcolumn</A></em>),
 then optionally convert to a raster map with
 <em><A HREF="v.to.rast.html">v.to.rast</A></em>.
 

vector/vectorintro.html

@@ -197,7 +197,7 @@ When creating vector maps from scratch, in general an attribute table must be cr
 the table must be populated with one row per category (using <a href="v.to.db.html">v.to.db</a>).
 However, this can be performed in a single step using <a href="v.db.addtable.html">v.db.addtable</a>
 along with the definition of table column types. Column adding and dropping
-can be done with <a HREF="v.db.addcol.html">v.db.addcol</a> and
+can be done with <a HREF="v.db.addcolumn.html">v.db.addcolumn</a> and
 <a HREF="v.db.dropcolumn.html">v.db.dropcolumn</a>. A table column can be renamed with
 <a HREF="v.db.renamecolumn.html">v.db.renamecolumn</a>. To drop a table from a map, use
 <a HREF="v.db.droptable.html">v.db.droptable</a>. Values in a table can be updated