GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages
grass-sqlite(1) GRASS GIS User's Manual grass-sqlite(1)

The SQLite driver is the default DBMI backend.

GRASS is automatically creating the SQLite database if it is not yet existing when the first table is created in the SQLite database. It is sufficient to define the connection (see next step).

The database name ’sqlite.db’ is at user’s choice. Also the file storage location can be freely chosen. If the database does not exist, it will be automatically created when database content is created:

# example for storing DB in mapset directory (keep single quotes):
db.connect driver=sqlite database=’$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite/sqlite.db’
db.connect -p

All SQL commands supported by SQLite (for limitations, see SQLite help page: SQL As Understood By SQLite and Unsupported SQL).

All SQL operators supported by SQLite.

A convenient SQLite front-end is sqlitebrowser. To open a DB file stored within the current mapset, the following way is suggested (corresponds to above database connection):

# fetch GRASS variables as shell environment variables:
eval `g.gisenv`
# use double quotes:
sqlitebrowser "$GISDBASE/$LOCATION_NAME/$MAPSET"/sqlite/sqlite.db

db.connect, db.execute, db.select
SQL support in GRASS GIS
SQLite web site, SQLite manual, sqlite - Management Tools

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

© 2003-2021 GRASS Development Team, GRASS GIS 7.8.6 Reference Manual

GRASS 7.8.6

Search for    or go to Top of page |  Section 1 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.