Repository files navigation

SeeLICENSE-AND-COPYRIGHTsection in ODBC.pm for usage and distribution rights.

Build, test and install Perl 5 (as per DBI specifications/compatibility)It is very important to TEST it and INSTALL it.Build, test and install the DBI module (at least DBI 1.609).It is very important to TEST it and INSTALL it.Remember to *read* the DBD::ODBC.pm POD documentation and theDBD::ODBC::Changes.pm POD documentation.

set-up these environment variables:

DBI_DSN   The dbi data source, e.g. 'dbi:ODBC:YOUR_DSN_HERE'DBI_USER  The username to use to connect to the databaseDBI_PASS  The username to use to connect to the databaseODBCHOME  (Unix only) The dir your driver manager is installed in          or specify this via -o argument to Makefile.PLDBD_ODBC_UNICODE Any value here will set the default install to                 attempt to turn on UNICODE support.

If you want UNICODE support on non-Windows platforms specify -uswitch to Makefile.PL. If you don't want UNICODE support on Windowsspecify the -nou switch to Makefile.PL. On non-Windows platforms allUNICODE features will work correctly with the unixODBC drivermanager.

If the Makefile.PL finds iODBC and you would prefer to build withunixODBC you can use the -x switch to favor unixODBC. This onlyhappens in rare case where you have binary packages of bothinstalled but you can only have development packages on oneinstalled and DBD::ODBC locates iODBC first. This quite oftenhappens on Ubuntu and other Debian based Linux systems where anincomplete iODBC is often installed.

perl Makefile.PL

make (or nmake/dmake, if VC++ on Win32)

make test (or nmake/dmake, if VC++ on Win32)

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 SQLserver driver up to SQL Server 2008 and many other ODBC drivers onWindows and UNIX (too numerous to mention here).

To run an individual test use:

prove -vb t/test.t

If the tests from t/09bind.t fail, that is an indication of lack ofODBC Level 2 functionality. This does not (necessarily) mean thatyour installation is broken. It does indicate that your ODBC driverdoes not support certain level 2 calls (see below). All other testsshould pass, however, since I've tested with a limited number ofODBC drivers, I could have something wrong in the test. Pleasenotify me if you have an incompatibility in the other tests. (Forexample, some Paradox ODBC driverscould fail, if they don'tsupport long file names, since in Paradox file names aretableName.db.). Please let me know about any incompatibilities youencounter. I will say, though, that I may not be able to reproduceor fix problems without some help, since I can't possibly installall the known ODBC drivers. Please try to "solve" the problem, inaddition 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.

This version utilizes at least one "Level 2" ODBC call(SQLDescribeParam). Thiswill affect compatibility with specificODBC drivers. If the driver is not level 2 (or does not support thelevel 2 function(s) required), then full compatibility will not beavailable. The best thing to do is build DBD::ODBC against an ODBCdriver manager like unixODBC (http://www.unixodbc.org) as it willresolve many incompatibilities between ODBC versions for you.

Do not hand edit the generated Makefile unless you are completelysure you understand the implications! Always try to make changes viathe Makefile.PL command line and/or editing the Makefile.PL.

You should not need to make any changes. If you doplease let meknow so that I can try to make it automatic in a later release.

This software is supported via the dbi-users mailing list. For moreinformation and to keep informed about progress you can join themailing list viahttp://dbi.perl.org (if you are unable to use theweb you can subscribe by sending a message todbi-users-subscribe@perl.org.

Please post details of any problems (or changes you needed to make)todbi-users@perl.org. But note...

** IT IS IMPORTANT TO INCLUDE THE FOLLOWING INFORMATION:

1. A complete log of a all steps of the build, e.g.:

perl Makefile.PL           (do a make realclean first)makemake testmake test TEST_VERBOSE=1   (if any tests fail)

2. Full details of which software you are using, including:

Perl version (the output of perl -V)ODBC Driver and versionODBC Driver manager used and version

It is important to check that you are using the latest versionbefore posting. If you're not then I'mvery likely to simply say"upgrade to the latest". You would do yourself a favour by upgradingbeforehand.

Please remember that I'mvery busy. Try to help yourself first,then try to help me help you by following these guidelinescarefully.

Regards,Tim, Jeff and Martin.