v.db.droptable(1)

πŸ’… v.db.droptable β€” the GRASS GIS manual, but make it make sense

okay bestie, so this is v.db.droptable from the GRASS GIS User's Manual. It's a lil command with one job and it does that job iconically. Let's get into it 🫢

✨ NAME ✨

v.db.droptable β€” removes an existing attribute table of a vector map. that's it. that's the whole vibe. bye table πŸ‘‹

🌸 KEYWORDS 🌸

vector, attribute table, database


⭐ SYNOPSIS ⭐

v.db.droptable
v.db.droptable --help
v.db.droptable [-f] map=name  [table=name]   [layer=string]   [--help]
[--verbose]  [--quiet]  [--ui]

πŸŽ€ Flags:

  • -f β€” Force removal (required for actual deletion of table). like, no -f, no deletion, periodt.
  • --help β€” Print usage summary
  • --verbose β€” Verbose module output
  • --quiet β€” Quiet module output
  • --ui β€” Force launching GUI dialog

πŸ¦‹ Parameters:

  • map=name [required] β€” Name of vector map. Or data source for direct OGR access.
  • table=name β€” Table name (default: vector map name)
  • layer=string β€” Layer number or name. Vector features can have category values in different layers. This number determines which layer to use. When used with direct OGR access this is the layer name. Default: 1

πŸ’– DESCRIPTION πŸ’–

v.db.droptable removes an existing attribute table from a given vector map linked at given layer. and like, real talk β€” if the -f force flag is not given then nothing is removed. nothing. zero. nada. the table stays exactly where it is. it's giving "safety feature" and honestly? slay for that πŸ”₯


🌈 NOTES 🌈

v.db.droptable is a front-end to db.execute to allow easier usage. so it's basically the cute lil spokesperson and db.execute is doing the actual heavy lifting behind the scenes, iykyk πŸ’…

The existing database connection(s) can be verified with v.db.connect. so if you're like "wait is anything even connected rn" β€” go check, bestie 🧚


✨ EXAMPLE ✨

Removing attribute table connected to layer 1:

g.copy vect=roadsmajor,myroads
v.db.droptable myroads
v.db.droptable myroads -f
v.db.connect -p myroads

see how the first v.db.droptable myroads has no -f? yeah. nothing happens there. it's a vibe check, not a deletion. then you hit it with the -f and boom, table's gone πŸ’€


πŸ‘‘ SEE ALSO πŸ‘‘

db.connect, db.execute, v.db.addtable, v.db.connect, v.db.dropcolumn, v.db.select, v.db.update

GRASS SQL interface


🌟 AUTHOR 🌟

Markus Neteler


πŸ“ SOURCE CODE πŸ“

Available at: v.db.droptable source code (history)

Accessed: Saturday Jan 17 05:41:52 2026

Main index | Vector index | Topics index | Keywords index | Graphical index | Full index

Β© 2003-2025 GRASS Development Team, GRASS GIS 8.4.2 Reference Manual

k that's the whole page, no cap 🫢 this was GRASS 8.4.2, v.db.droptable(1), documented up and down, accessed Saturday Jan 17 05:41:52 2026, brought to you by the Β© 2003-2025 GRASS Development Team and their GRASS GIS 8.4.2 Reference Manual. go drop a table, but like, use the -f first. mwah πŸ’‹

πŸ“¦ where this page comes from