Using MySQL 5.1 for Data Warehousing/Business Intelligence Overview


 
Thread Tools Search this Thread
Top Forums Web Development MySQL DevZone RSS Using MySQL 5.1 for Data Warehousing/Business Intelligence Overview
# 1  
Old 11-25-2008
Using MySQL 5.1 for Data Warehousing/Business Intelligence Overview

Breadboard BI provides affordable business intelligence (BI), data integration, and general software application development consulting. We also offer a suite of customizable BI modules that form a modular and scalable enterprise solution. Our mission is to provide products and service that enable companies to reduce costs, improve sales, and satisfy regulatory requirements.

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
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)