1databaseintro(1) Grass User's Manual databaseintro(1)
2
3
4
6 Attribute management in general
7 GRASS can be linked to one or many database management systems (DBMS).
8 The db.* set of commands provides basic SQL support for attribute man‐
9 agement, while the v.db.* set of commands operates on the vector map
10 (see Vector introduction).
11
12 Available drivers
13 Available drivers are listed in SQL support in GRASS GIS.
14
15 Notes:
16 The default DBF driver provides only very limited SQL support (as DBF
17 is not an SQL DB) while the other DBMS backends (such as PostgreSQL,
18 MySQL etc) provide full SQL support since the SQL commands are sent
19 directly to the DBMS.
20
21 SQL commands
22 SQL commands can be directly executed with db.select and the other db.*
23 modules. See the SQL help page for examples.
24
25 Managing the default settings
26 Per default vector map attributes are stored in DBF table files. This
27 default definition can be modified with db.connect. If an external DBMS
28 is used, db.login may be required.
29
30 Creating a database
31 Specific commands are explained on the individual driver pages (these
32 pages are only available if driver was compiled in this installation):
33
34 DBF: see DBF page
35
36 SQLite: SQLite page
37
38 mySQL: meSQL pages
39
40 ODBC: ODBC page (connect to Oracle, etc.)
41
42 PostgreSQL: PostgreSQL and PostGIS page
43 Conversion tools:
44 MDB Tools: Convert MS-Access data to SQL, DBF, etc. Example:
45 gmdb dbfile.mdb
46
47
48 Database Schema
49 Currently schema support only works for PostgreSQL connections. Default
50 schema can be set with db.connect. Note that the default schema will be
51 used by all db.* modules.
52
53 db.tables returns 'schema.table' if schemas are available in the data‐
54 base.
55
56 See also
57 Introduction to GRASS vector map processing
58
59 Introduction to GRASS raster map processing
60 Main index - database index - full index
61
62 Last changed: $Date: 2006/08/24 19:11:36 $
63
64
65
66GRASS 6.2.2 databaseintro(1)