grass-mesql(1grass) [debian man page]

grass-mesql(1grass)						Grass User's Manual					       grass-mesql(1grass)

NAME

       grass-mesql - MySQL embedded driver

       MySQL  embedded	driver	MySQL  embedded  driver  in GRASS MySQL database driver in GRASS enables GRASS to store vector attributes in MySQL
       embedded database without necessity to run MySQL server.

Driver and database name
       GRASS modules require 2 parameters to connect to a database.  Those parameters are 'driver' and 'database'. For MySQL embedded  driver  the
       parameter  'driver'  should  be	set  to value 'mesql'.	The parameter 'database' is a full path to the directory where database tables are
       stored. The best place is a directory in the mapset. The directory must be created before use of the driver. In the name of database it	is
       possible to use 3 variables:

		      $GISDBASE - path to current GISBASE

		      $LOCATION_NAME - name of current location

		      $MAPSET - name of current mapset

       Examples of connection parameters:
	 db.connect driver=mesql database='$GISDBASE/$LOCATION_NAME/$MAPSET/mysql'
	 db.connect driver=mesql database=/home/user1/db

Data types, indexes
       For more informations about supported data types and indexes see the documentation for MySQL (mysql) driver

Database type
       Because	database  closing  was	found  very  slow if InnoDB was used, the InnoDB storage is disabled by default (hardcoded '--skip-innodb'
       server option).

Note
       The embedded server is started with hardcoded '--bootstrap' option to avoid warning about missing mysql.time_zone_leap_second  table.  This
       can be fixed in future.

SEE ALSO

	db.connect, SQL support in GRASS GIS

Credits
       Development of the driver was sponsored by Faunalia (Italy) as part of a project for ATAC.

AUTHOR

       Radim Blazek

       Last changed: $Date: 2011-02-07 18:59:50 +0100 (Mon, 07 Feb 2011) $
       Help Index

GRASS 6.4.2														       grass-mesql(1grass)

grass-odbc(1grass)						Grass User's Manual						grass-odbc(1grass)

NAME

       grass-odbc - ODBC driver

       ODBC driver ODBC driver in GRASS Communication between GRASS and ODBC database for attribute management:
       | GRASS module | | ODBC Interface | | RDBMS
       | GRASS | DBMI driver | unixODBC | ODBC driver | PostgreSQL
       | Oracle
       | ...

Supported SQL commands
       All SQL commands supported by ODBC.

Operators available in conditions
       All SQL operators supported by ODBC.

EXAMPLE

       In  this  example  we  copy  the  dbf file of a SHAPE map into ODBC, then connect GRASS to the ODBC DBMS. Usually the table will be already
       present in the DBMS.

		     Configure ODBC driver for selected database (manually or with 'ODBCConfig').  ODBC drivers are defined in	/etc/odbcinst.ini.
		     Here is example:
		      [PostgreSQL]
		      Description     = ODBC for PostgreSQL
		      Driver	      = /usr/lib/libodbcpsql.so
		      Setup	      = /usr/lib/libodbcpsqlS.so
		     FileUsage	     = 1

		      Create  DSN  (data  source  name).  The  DSN  is	used  as  database  name  in  db.*   modules.  Then DSN must be defined in
		     $HOME/.odbc.ini (for this user only) or in /etc/odbc.ini for (for all users) [watch out for the database name  which  appears
		     twice and also for the PostgreSQL protocol version]. Omit blanks at the beginning of lines:
		      [grass6test]
		      Description	      = PostgreSQL
		      Driver		      = PostgreSQL
		      Trace		      = No
		      TraceFile 	      =
		      Database		      = grass6test
		      Servername	      = localhost
		      UserName		      = neteler
		      Password		      =
		      Port		      = 5432
		      Protocol		      = 8.0
		      ReadOnly		      = No
		      RowVersioning	      = No
		      ShowSystemTables	      = No
		      ShowOidColumn	      = No
		      FakeOidIndex	      = No
		     ConnSettings	      =  Configuration	of  an	DSN without GUI is described on http://www.unixodbc.org/odbcinst.html, but
		     odbc.ini and .odbc.ini may be created by the 'ODBCConfig' tool. You can easily view your DSN structure by 'DataManager'. Con-
		     figuration with GUI is described on http://www.unixodbc.org/doc/UserManual/

	      To find out about your PostgreSQL protocol, run:

	      psql -V

		     Now create a new database if not yet existing:
		     db.createdb driver=odbc database=grass6test

		     Now store the table 'mytable.dbf' (here: in current directory) into PostgreSQL through ODBC:
		     db.connect driver=odbc database=grass6test
		     db.copy from_driver=dbf from_database=./ from_table=mytable 
			     to_driver=odbc to_database=grass6test to_table=mytable

		      Next link map to attribute table (now the ODBC table is used, not the dbf file):
		     v.db.connect map=mytable.shp table=mytable key=ID 
				  database=grass6test driver=odbc
		     v.db.connect -p

		     Finally a test: Here we should see the table columns (if the ODBC connection works):
		     db.tables -p
		     db.columns table=mytable
		      Now the table name 'mytable' should appear.
		     Doesn't work? Check with 'isql ' if the ODBC-PostgreSQL connection is really established.
       Note  that  you	can  also connect mySQL, Oracle etc. through ODBC to GRASS.  You can also check the vector map itself concerning a current
       link to a table:
       v.db.connect -p mytable.shp
	which should print the database connection through ODBC to the defined RDBMS.

SEE ALSO

	db.connect, v.db.connect, unixODBC web site, SQL support in GRASS GIS

       Last changed: $Date: 2011-02-07 18:59:50 +0100 (Mon, 07 Feb 2011) $
       Help Index

GRASS 6.4.2															grass-odbc(1grass)