New development release (1.18_2) of DBD::ODBC - please read if you use DBD::ODBC

Hi,

I have released a new development release of DBD::ODBC 1.18_2 which you 
can find on CPAN. For a list of changes see the end of this email.

I would like to make a plea to all DBD::ODBC users to download and at 
least run the make test and send the output to me, even if you are not 
currently planning on upgrading.

Increasingly I am finding it very difficult to keep on top of specific 
workarounds for drivers and driver managers. At this time there are at 
least 4 ODBC driver managers and well over 50 ODBC drivers used 
regularly (just for SQL Server on Windows there are over 10 drivers and 
versions which can be used for SQL Server). I cannot possibly have and 
test them all and fixing an issue in one driver/driver_manager is 
increasingly likely to break another sending me into a loop.

The latest test code for DBD::ODBC outputs details of the database and 
driver which I can use to create a matrix of working versions. Please, 
please at least download the latest DBD::ODBC, run make test and send it 
to me.

Issues addressed in 1.18_1 and 1.18_2:

=head2 Changes in DBD::ODBC 1.18_2 March 9, 2009

Added yet another workaround for the SQL Server Native Client driver
version 2007.100.1600.22 and 2005.90.1399.00 (driver version
09.00.1399) which leads to HY104, "Invalid precision value" in the
rt_39841.t test.

=head2 Changes in DBD::ODBC 1.18_1 March 6, 2009

Fixed bug reported by Toni Salomäki leading to a describe failed error
when calling procedures with no results. Test cases added to
20SqlServer.t.

Fixed bug rt 43384 reported by oyse where you cannot insert more than
127 characters into a Microsoft Access text(255) column when DBD::ODBC
is built in unicode mode.

Martin
-- 
Martin J. Evans
Easysoft Limited
http://www.easysoft.com