Provided by: grass-doc_6.4.3-3_all bug

NAME

       db.connect  - Prints/sets general DB connection for current mapset and exits.

KEYWORDS

       database, attribute table, connection settings

SYNOPSIS

       db.connect
       db.connect help
       db.connect   [-pc]   [driver=name]    [database=name]    [schema=string]    [group=string]
       [--verbose]  [--quiet]

   Flags:
       -p
           Print current connection parameters and exit

       -c
           Check connection parameters, set if uninitialized, and exit

       --verbose
           Verbose module output

       --quiet
           Quiet module output

   Parameters:
       driver=name
           Driver name
           Options: sqlite,mysql,odbc,pg,dbf,ogr
           Default: dbf

       database=name
           Database name
           Default: $GISDBASE/$LOCATION_NAME/$MAPSET/dbf/

       schema=string
           Database schema
           Do not use this option if schemas are not supported by driver/database server

       group=string
           Default group of database users to which select privilege is granted

DESCRIPTION

       db.connect allows the user to set database connection parameters.   These  parameters  are
       then  taken  as  default  values  by  modules  so that the user does not need to enter the
       parameters each time.

NOTES

       Values are stored in the mapset's VAR file; the connection is not tested for validity.

       The -p flag will display the current connection parameters.

       The -c flag will silently check if the connection parameters have been  set,  and  if  not
       will  set  them  to  use GRASS's default values.  (useful in scripts before you attempt to
       create a new database table)

       To connect a vector map to a database table, use v.db.connect or v.db.addtable.

EXAMPLES

   DBF
       Local storage (the dbf/ subdirectory in the mapset must exist or must be  created  by  the
       user):

       db.connect driver=dbf database='$GISDBASE/$LOCATION_NAME/$MAPSET/dbf/'
       db.tables -p

   SQLite
       Local storage:

       db.connect driver=sqlite database='$GISDBASE/$LOCATION_NAME/$MAPSET/sqlite.db'
       db.connect -p
       db.tables -p

       The SQLite database is created automatically when used the first time.

   ODBC
       Network storage: (may require the use of db.login):

       db.connect driver=odbc database=gtest
       db.login user=myname [pass=secret]
       db.connect -p
       db.tables -p

   PostgreSQL
       Network storage: (may require the use of db.login):

       db.connect driver=pg database="host=myserver.itc.it,dbname=mydb"
       db.login user=myname [pass=secret]
       db.connect -p
       db.tables -p

   PostgreSQL with different port
       Network storage: (may require the use of db.login):

       db.connect driver=pg database="host=myserver.itc.it,dbname=mydb,port=6666"
       db.login user=myname [pass=secret]
       db.connect -p
       db.tables -p

   MySQL (local)
       Local storage (db.login may not be needed):

       db.connect driver=mysql database=mydb
       db.login user=myname [pass=secret]
       db.connect -p
       db.tables -p

   MySQL (external server)
       Network storage: (may require the use of db.login):

       db.connect driver=mysql database="host=myserver.itc.it,dbname=mydb"
       db.login user=myname [pass=secret]
       db.connect -p
       db.tables -p

SEE ALSO

         db.columns,  db.drivers,  db.login,  db.tables,  v.db.addtable,  v.db.connect, GRASS SQL
       interface

AUTHOR

       Radim Blazek, ITC-Irst, Trento, Italy

       Last changed: $Date: 2011-11-08 01:42:51 -0800 (Tue, 08 Nov 2011) $

       Full index

       © 2003-2013 GRASS Development Team