db.droptable(1grass)
π db.droptable β the GRASS manual, but make it slay π
okay bestie, so this one is db.droptable from the GRASS User's Manual, and it's literally the girl who deletes stuff for you (only when you tell her to). Let's get into it π
β¨ NAME β¨
db.droptable β drops an attribute table. that's it, that's the whole job. goodbye table bestie π
π 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β the force flag. this is the one that actually lets files get deleted. without it, nothing happens. respect the-f, fr fr--helpβ prints the usage summary so you're not out here guessing π--verboseβ verbose module output, i.e. she tells you everything--quietβ quiet module output, i.e. she says nothing, mysterious queen--uiβ forces the GUI dialog to launch. graphic design is her passion π¨
π Parameters:
driver=nameβ name of the database driver. if you don't give one, the default driver gets used. no capdatabase=nameβ name of the database. if you don't give one, the default database gets used. periodttable=nameβ required. name of the table to drop. you literally cannot skip this one, she needs to know who she's dropping
π DESCRIPTION π
db.droptable drops an attribute table. simple. iconic.
but here's the plot twist bestie: if you do not pass the -f force flag, then nothing gets removed. instead, she just prints a preview of the action she would take. it's giving "here's what I would do to you" energy, and honestly? respect. it's a vibe check before the actual delete π₯
πΈ NOTES πΈ
db.droptable is a front-end to db.execute, made so your life is easier. to some extent it also verifies whether the table is connected to a vector map β you know, to avoid accidental table removal π because accidentally deleting a table is a tragedy and we don't do tragedies here π«Ά
bestie, the "avoid accidental table removal" thing is a safety net, not a promise. stay awake.
β¨ 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
see how the first db.droptable is just the preview? that's the no -f life. then -f comes in and actually does the deed π
π§ Removing an attribute table from given database
db.droptable lets you optionally define driver and database options that are different from your default connection settings (db.connect -p). so you can go somewhere else entirely, main character behavior.
# drop the table from SQLite database
db.droptable -f table=sometable driver=sqlite database=/opt/sqlite.db
look at that path. look at that driver. she's versatile π
π«Ά 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: Wednesday Mar 12 22:27:28 2025 in commit: 0095480779ff07f10b76a859388850c52b9dccbd
Main index | Database index | Topics index | Keywords index | Graphical index | Full index
Β© 2003-2026 GRASS Development Team, GRASS 8.5.0 Reference Manual
and that's the whole page, bestie π this was db.droptable(1grass) from the GRASS User's Manual, running on GRASS 8.5.0, with that last change landing Wednesday Mar 12 22:27:28 2025 β go forth, drop tables responsibly, and always remember the -f πβ¨
π¦ where this page comes from
- alpine 3.24: grass-gis-doc 8.5.0-r1 Β· GPL-2.0-or-later
- ubuntu stonking: grass-doc 8.5.0-1ubuntu1 Β· GPL-2.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms