Documentation in .CHM and .HLP format has been removed from the distribution. (Bug#56232)

For some procedure and parameter combinations SQLProcedureColumns() did not work correctly. For example, it could not return records for an existing procedure with correct parameters supplied.

Further, it returned incorrect data for column 7, TYPE_NAME. For example, it returned VARCHAR(20) instead of VARCHAR. (Bug#57182)

The MySQL Connector/ODBC MSI installer did not set the InstallLocation value in the Microsoft Windows registry. (Bug#56978)

In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the uploaded data contained errors, such as primary key duplication, and foreign key violation. (Bug#56804)

SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if the query was parameterized and not all parameters were bound.

Note, MSDN states that “For performance reasons, an application should not call SQLColAttribute/SQLDescribeCol before executing a statement.” However, it should still be possible to do so if performance reasons are not paramount. (Bug#56717)

When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the driver ran SET @@sql_select_limit=1, which limited the resultset to just one row. (Bug#56677)

After installing MySQL Connector/ODBC, the system DSN created could not be configured or deleted. An error dialog was displayed, showing the error message “Invalid attribute string”.

In this case the problem was due to the fact that the driver could not parse the NULL-separated connection string. (Bug#56233)

When used after a call to SQLTables(), SQLRowCount() did not return the correct value. (Bug#55870)

When attempting to install the latest Connector/ODBC 5.1.6 on Windows using the MSI, with an existing 5.1.x version already installed, the following error was generated:

Another version of this product is already installed.  Installation of this version
cannot continue.  To configure or remove the existing version of this product, use
Add/Remove Programs on the Control Panel.

Also, the version number displayed in the ODBC Data Source Administrator/Drivers tab did not get updated when removing or installing a new version of 5.1.x. (Bug#54314)