Package org.griphyn.vdl.dbdriver

Provides for the database driver encapsulation.

See:
Description

Class Summary

DatabaseDriver	This common database interface that defines basic functionalities for interacting with backend SQL database.
MySQL	This class implements the driver API for the MySQL 4.* database.
Oracle	This class implements the driver API for the production strength rDBMS by Oracle.
Postgres	This class implements the driver API for the PostGreSQL 7.3.* and 7.4.* series database.
SQLite	This class implements the driver API for the free, small, and fast file-based SQL Lite.
SQLServer2000	This class implements the driver API for the Microsoft SQL Server 2000 database.

Package org.griphyn.vdl.dbdriver Description

Provides for the database driver encapsulation.

Package Specification

The classes in this package provide an implementation for different relational database management backend systems. The correct backend system is dynamically instantiated, steered through properties.

Shown in black are implemented drivers. Red and black show non-working implementations. In red are shown projected drivers that won't work at all.

To provide an alternative implementation for an rDBMS, you need to extend DatabaseDriver.

Related Documentation

For overviews, tutorials, examples, guides, and tool documentation, please see:

• GVDS
• Chimera
• GriPhyN

The following properties are understood by most if not all JDBC drivers. Please note the GVDS-specific prefix. The asterisk should either be used literally, meaning that the driver configuration applies to all catalogs, or with the appropriate catalog abbreviation (vdc, ptc, tc):

vds.db.*.driver

This property names the class that implements the DatabaseDriver for a specific database engine. If the value is a identifier without periods, the prefix org.griphyn.vdl.dbdrivers. is assumed. Otherwise, the value denotes the complete Java path to the implementing class. Being a class name, capitalization is important.

vds.db.*.driver.url

The URL under which a database may be access. This URL is often specific to the database itself. However, usually it contains the host and port (or file) to contact the rDBMS, and the name of the database within the rDBMS.

vds.db.*.driver.user

This property specifies the name of the database user as which to connect to the database.

vds.db.*.driver.password

The password property specifies the password of the database user.

See Also:

org.griphyn.vdl.dbschema