DBI-1.21.patch1 
===============

Mail and patch from dbi-dev for problem with dispatch and make test with
TRACE=1

DBD-ODBC-0.33_3.patch
=====================
This patch does the following:
[1] fixes table_info to allow qualifiers
[2] adds primary_key_info

This patch was sent to Jeff Urlwin Jan 2002.

Note about DBD::ODBC 0.28, 0.32 and 0.33_1 (test release)
=========================================================

DBD::ODBC parses your SQL looking for placeholders.
To prevent plain text in your SQL being mistakenly identified as a
placeholder you put the SQL text in quotes. The quoting character used
in DBD::ODBC changed with released versions as follows:

DBD::ODBC 0.28 - used '
DBD::ODBC 0.32 - used "
DBD::ODBC 0.33_1 - used " and '

DBD-ODBC-0.28.patch1
====================

This patch does the following:
[1] fix trace message coredumping after SQLDriverConnect
[2] fix call to SQLCancel which fails to pass the statement handle properly.
[3] consume diagnostics after SQLDriverConnect/SQLConnect call or they remain
    until the next error occurs and it then looks confusing (this is due to
    ODBC spec for SQLError). e.g. test 02simple returns a data truncated error
    only now instead of all the informational diags that are left from the
    connect call, like the "database changed", "language changed" messages you
    get from MS SQL Server.
[4] remove C++ comments - they are annoying on platforms where the compiler
    does not support them.

It was sent to Jeff Urlwin and is incorporated in later DBD::ODBC releases.

DBI-1.10
========

Important Note:

The DBI-1.10 version of DBI is known to have a few problems
with undefined usernames and passwords in the calls to DBI->connect.

If you get errors like 'Can't locate object method "default_user"'
then you either obtain Tim Bunce's patch for DBI, use DBI-1.09 or
ensure that you're calling DBI->connect with defined
values for $user and $pass.

See the DBI mailing list for more information.