***************************************************************
* This code is LGPL. You CAN make commercial solutions using  *
* LGPL software.                                              *
***************************************************************

+-------------------------------------------------------------+
| unixODBC                                                    |
| Driver Manager                                              |
+-------------------------------------------------------------+

This is the traffic Cop for unixODBC. It is the hub of most
ODBC activity but its function is fairly minimal. 90% of the
Driver Managers job is to;

1. validate arguments
2. load/unload a driver
3. call a driver function to do the work

In fact, prior to unixODBC, most drivers were expected to operate
without a DriverManager on Linux.

Despite its simple function; the DriverManager is key in providing
one of the two main benefits of ODBC... runtime binding. This
runtime binding allows the application user to select what type
of data source (ie MiniSQL, Sybase, PostgreSQL, etc, or a file based
data source...) and to be able to change it without modification
or recompiling of the application.

Not all functions are complete however, all functions SHOULD defer
to the driver in anycase so if the driver does the function then
the lack of any processing by Driver Manager should be irrelevent.

The key thing to be completed in the Driver Manager is to implement
function mapping to provide, as much as possible, a 3.51 function
even when dealing with older drivers.

+-------------------------------------------------------------+
| http://genix.net/unixODBC                                   |
| Nick Gorham <nick.gorham@easysoft.com>                      |
| Peter Harvey <pharvey@codebydesign.com>                     |
| 9.MAY.99                                                    |
+-------------------------------------------------------------+


