DBD-ODBC 1.13

DBD-ODBC module provides you an ODBC driver for DBI.

TESTING

make test
make test TEST_VERBOSE=1 (if any of the t/* tests fail) make install (if the tests look okay)

Note that the tests currently all pass when using the Microsoft SQL server driver. See the known compatibility list below.

If the tests from t/09bind.t fail, that is an indication of lack of ODBC Level 2 functionality. This does not (necessarily) mean that your installation is broken. It does indicate that your ODBC driver does not support certain level 2 calls (see below). All other tests should pass, however, since I've tested with a limited number of ODBC drivers, I could have something wrong in the test. Please notify me if you have an incompatibility in the other tests. (For example, some Paradox ODBC drivers *could* fail, if they don't support long file names, since in Paradox file names are tableName.db.). Please let me know about any incompatibilities you encounter (I'm sure you will). I will say, though, that I may not be able to reproduce or fix problems without some help, since I can't possibly install all the known ODBC drivers. Please try to "solve" the problem, in addition to discovering it.

If any of the tests fail and you are using SQL Server and Windows drivers, ensure you updated to MDAC 2.7 or later.

NOTES on ODBC Drivers and Compatibility with DBD-ODBC

This version utilizes at least one "Level 2" ODBC call (SQLDescribeParam). This *will* affect compatibility with specific ODBC drivers. If the driver is not level 2 (or does not support the level 2 function(s) required), then full compatibility will not be available.

DBD-ODBC currently uses SQLDescribeParam for binding parameters to queries. You may (and probably will) have success using DBD-ODBC without binding parameters.