GRASS logo

NAME

db.droptable - Drops an attribute table.

KEYWORDS

database, attribute table

SYNOPSIS

db.droptable
db.droptable --help
db.droptable [-f] [driver=name] [database=name] table=name [--help] [--verbose] [--quiet] [--ui]

Flags:

-f
Force removal (required for actual deletion of files)
--help
Print usage summary
--verbose
Verbose module output
--quiet
Quiet module output
--ui
Force launching GUI dialog

Parameters:

driver=name
Name of database driver
If not given then default driver is used
database=name
Name of database
If not given then default database is used
table=name [required]
Name of table to drop

Table of contents

DESCRIPTION

db.droptable drops an attribute table. If the -f force flag is not given then nothing is removed, instead a preview of the action to be taken is printed.

NOTES

db.droptable is a front-end to db.execute to allow easier usage. To some extent it is verified if the table is connected to a vector map to avoid accidental table removal.

EXAMPLES

Removing an attribute table from default database

# show default database
db.connect -p

# show available tables
db.tables -p

# this will show what would happen
db.droptable table=sometable

# actually drop the table
db.droptable -f table=sometable

Removing an attribute table from given database

db.droptable allows defining optionally driver and database options different from default connection settings (db.connect -p).
# drop the table from SQLite database
db.droptable -f table=sometable driver=sqlite database=/opt/sqlite.db

SEE ALSO

db.dropdb, db.dropcolumn, db.execute, db.login, db.connect, db.tables, db.describe, v.db.droptable,

GRASS SQL interface

AUTHORS

Markus Neteler
Driver and database options added by Martin Landa, Czech Technical University in Prague, Czech Republic

SOURCE CODE

Available at: db.droptable source code (history)

Latest change: Thursday Feb 03 11:10:06 2022 in commit: 547ff44e6aecfb4c9cbf6a4717fc14e521bec0be


Main index | Database index | Topics index | Keywords index | Graphical index | Full index

© 2003-2023 GRASS Development Team, GRASS GIS 8.2.2dev Reference Manual