New 1.50 release of DBD::ODBC

I've just uploaded DBD::ODBC 1.50 to the CPAN. This is the culmination of a series of 4 development releases in the 1.49 series. There are a number of bug fixes, enhancements, deprecated features and most importantly some changes in behaviour. See below for a list of changes.

1.50 2014-07-25

   [BUG FIXES]

   The 80_odbc_diags.t test could fail if a driver fails a table does
   not exist test in the prepare instead of the execute.

1.49_4 2014-07-08

   [BUG FIXES]

   Fixed sql_type_cast.t test which assumed column aliases which stay
   lowercase.

   Fixed 87_odbc_lob_read.t test which did not bow out of the test
   properly if the database was not MS SQL Server.

   [DOCUMENTATION]

   Revised the query notification example and documentation.

   Added a link to a better Query Notification article.

1.49_3 2014-05-01

   [CHANGE IN BEHAVIOUR]

   As warned years ago, this release removes the odbc_old_unicode attribute.
   If you have a good reason to use it speak up now before the next non-development
   release.

   [BUG FIXES]

   Fix rt89255: Fails to create test table for tests using PostgreSQL odbc driver.
   Change test suite to fallback on PRECISION if COLUMN_SIZE is not found.

   [ENHANCEMENTS]

   Added support for MS SQL Server Query Notification. See the new
   section in the pod.

   Added a currently undocumented (and experimental)
   odbc_describe_param method on a statement handle which takes a
   parameter number as the only argument and returns an array of the
   data type, parameter size, decimal digits and nullable (as per
   SQLDescribeParam).

   [DOCUMENTATION]

   Added FAQ on truncated column names with freeTDS.

   [MISCELLANEOUS]

   I have removed the "experimental" tag for odbc_getdiagfield and odbc_getdiagrec
   methods.

1.49_2 2014-04-26

   [BUG FIXES]

   Change to data_sources in 1.49_1 could lead to a compile error since
   data_sources was not returning a value if an error occurred.

1.49_1 2014-04-25

   [BUG FIXES]

   If you had a lot of DSNs on Windows (more than 280 but it depends on
   the length of their names) and called the data_sources method it
   could crash your script. Code internally changed to stop putting the DSNs
   returned on the stack.

   [CHANGE IN BEHAVIOUR]

   As warned years ago, the private data_sources method has been
   removed - use DBI one instead.

   [MISCELLANEOUS]

   Added FAQ entry of maximum number of allowed parameters.

Martin