Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

dbf2mysql parameter, WWWXXXAPC, wwwxxxAPC, How to unsubscrube from dategen spam, docmd.close 2585, WWWXXXDOCO, nu vot, dhcpd lease file "binding state", WWWXXXDOCO, how to setup procmail to process html2text



#1: MySQL Connector/ODBC 3.51.16 is available!

Posted on 2007-06-15 23:20:55 by Jim Winstead

Dear MySQL users,

MySQL Connector/ODBC 3.51.16, a new version of the ODBC driver for the
MySQL database system, has been released. This release is the latest
release of the 3.51 series and is suitable for use with any MySQL
version including MySQL 4.1, 5.0, or 5.1.


While we consider this a production release, we recommend caution in
upgrading due to changes in our build procedures, and the large number
of bug fixes that have gone into the most recent releases.

The release is now available in source and binary form for a number of
platforms from our download pages at

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.:

Platform notes:
* There are no binary packages for Microsoft Windows x64 Edition.
* The Mac OS X binary packages are only provided as tarballs, there is no
* There is no binary package for Mac OS X on 64-bit PowerPC because Apple
does not currently provide a 64-bit PowerPC version of iODBC.
* The HP-UX 11.23 IA64 binary package does not include the GUI bits because
of problems building Qt on that platform.
* The binary packages for Sun Solaris are only provided as tarballs, not
the PKG format.

Changes since the last release:

Functionality added or changed:
* Added support for using SSL. This is not yet exposed in the setup GUI,
but must be enabled through configuration files or the DSN. (Bug #12918)

Bugs fixed:
* Statements that return multiple result sets (such as calls to stored
procedures) would not free all results when closed. (Bug #27544)
without seperators, which could cause them to get interpreted incorrectly
in some cases due to server bugs. (Bug #15773)
* Calls to SQLNativeSql() could cause stack corruption due to an incorrect
pointer cast. (Bug #28758)
* SQLSetPos() could update or delete the wrong rows when the original result
set did not contain all columns of a multi-part primary key. (Bug #28255)
* SQLTables() did not distinguish tables from views. (Bug #23031)
* The wrong function was used for freeing the artificial result sets that
are created by some catalog functions. (Bug #22797)
* Accessing the results of catalog functions could cause a crash when the
"Don't cache results" option was set and a forward-only cursor was
being used. (Bug #4657)
* SQL_WVARCHAR and SQL_WLONGVARCHAR parameters were not properly quoted
and escaped. (Bug #16235)
* SQLForeignKeys() did not properly escape wildcard characters in its
table name parameters when retrieving information. (Bug #27723)
* Calls to SQLSetPos() could cause the driver to incorrectly calculate the
length of some fields. (Bug #16917)

MySQL ODBC Mailing List
For list archives:
To unsubscribe:

Report this message