
README file for the DWI db_drivers directory
--------------------------------------------
Multiple backends are supported for the database access, including 
ODBC, LibDBI, and the native Postgres backend.   If you are a user
of DWI, just pick the one you want, and compile with that.  Do this
by editing the Makefile and picking the -DUSE_XXX that you want.
Pakcage maintainers should compile with all three of course, although
the dynamic loading means that the package does not have to depend on 
all three.

To use the Postgres Native driver, set -DUSE_LIBPG_FE  

To use libdbi (http://libdbi.sourceforge.net), set -DUSE_LIBDBI.  

To compile the iODBC (http://www.iodbc.org) bindings, set -DUSE_ODBC in
the Makefile.  

You can set any/all at once, since this system uses a plugin
architecture.

You can also create new plugins for different SQL DB drivers very easily.
Look at the libdbi sources for a good example of how little it can take.

Its probably recommended that you use either the libdbi driver, or 
the postgres-native driver.  Personally, I find ODBC hard to configure 
and hard to use.  ODBC seems to be very poorly designed.

