-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I released DBD::ODBC 1.20 yesterday. I am happy to accept any make test
results mailed directly to me whether they are success or failure. If
you mail me success results I'll compile a listing of working ODBC drivers.

The changes are listed below the most significant of which are the first
and last ones. There is currently a problem with SQL Server Native
Client version 10.00.1600 which I am still working on reported via cpan
testers. If you have this version of SQL Server Native Client and are
prepared to help me out running some test code I would like to hear from
you as I'm having problems getting it myself.

=head2 Changes in DBD::ODBC 1.20 April 20, 2009

Fix bug in handling of SQL_WLONGVARCHAR when not built with unicode
support.  The column was not identified as a long column and hence the
size of the column was not restricted to LongReadLen. Can cause
DBD::ODBC to attempt to allocate a huge amount of memory.

Minor changes to Makefile.PL to help diagnose how it decided which
driver manager to use and where it was found.

Offer suggestion to debian-based systems when some of unixODBC is
found (the bin part) but the development part is missing.

In 20SqlServer.t attempt to drop any procedures we created if they
still exist at the end of the test. Reported by Michael Higgins.

In 12blob.t separate code to delete test table into sub and call at
being and end, handle failures from prepare there were two ENDs.

In ODBCTEST.pm when no acceptable test column type is found output all
the found types and BAIL_OUT the entire test.

Skip rt_39841.t unless actually using the SQL Server ODBC driver or
native client.

Handle drivers which return 0 for SQL_MAX_COLUMN_NAME_LEN.

Double the buffer size used for column names if built with unicode.

Martin
- --
Martin J. Evans
Easysoft Limited
http://www.easysoft.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ7fahhd1KVpsamNgRAvuiAJ9WPX0i0XTPhSEQHCP74tMzOlXjSACeMJCJ
2DOHe1V7VG2XypyeaRMBFeU=
=himF
-----END PGP SIGNATURE-----

Reply via email to