From: Kent Boortz Date: May 4 2012 10:52am Subject: MySQL Connector/ODBC 5.1.11 has been released List-Archive: http://lists.mysql.com/myodbc/11737 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Dear MySQL users, MySQL Connector/ODBC 5.1.11, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the latest release of the 5.1 series and is suitable for use with any MySQL version since 4.1 (It will not work with 4.0 or earlier releases.). The release is now available in source and binary form for a number of platforms from our download pages at http://dev.mysql.com/downloads/connector/odbc/5.1.html and mirror sites. Note that not all mirror sites may be up to date at this point in time, so if you can't find this version on some mirror, please try again later or choose another download site. We welcome and appreciate your feedback, bug reports, bug fixes, patches, etc.: http://forge.mysql.com/wiki/Contributing Enjoy! The MySQL build team at Oracle ========== Functionality Added or Changed * A new connection option, prefetch, allows applications to scroll through large query result sets, N records at a time. See Section 22.1.4.2, "Connector/ODBC Connection Parameters" for details. Bugs Fixed * The SQLTables() function did not return the catalog correctly if the wildcard or SQL_ALL_CATALOGS was used. (Bug #13914518) * The fraction member in SQL_TIMESTAMP_STRUCT was always set to 0 when a timestamp was retrieved using SQLGetData(). The fix causes the fraction member to be correctly set, with a value representing nanoseconds. This issue did not occur when a result was retrieved as a string (SQLGetData() with SQL_C_CHAR). (Bug #12767740, Bug #60646) * Fractional seconds part of timestamp was ignored in prepared statements that use SQLBindParameter and SQL_C_TIMESTAMP type. For example, a prepared query comparing two timestamp values that only differed in the fractional part would consider the values identical. (Bug #12767761, Bug #60648) * On Windows platforms, some memory was leaked on each connection attempt due to an incorrect response to a SQLGetDiagRec() call. (Bug #11766029, Bug #59059) -- Kent Boortz, Release Staff engineer Oracle, the MySQL team Office: +46 863 11 363 Mobile: +46 76 77 69 049