Accessing a parameter with the type of
SQL_C_CHAR, but with a numeric type and a
length of zero, the parameter marker would get stripped from the
query. In addition, an SQL injection was possible if the
parameter value had a nonzero length and was not numeric, the
text would be inserted verbatim.
In previous versions, the SSL certificate would automatically be
verified when used as part of the MySQL Connector/ODBC connection. The
default mode is now to ignore the verificate of certificates. To
enforce verification of the SSL certificate during connection,
SSLVERIFY DSN parameter, setting the
value to 1.
(Bug #29955, Bug #34648)
When using ADO, the count of parameters in a query would always return zero. (Bug #33298)
Using tables with a single quote or other nonstandard characters in the table or column names through ODBC failed. (Bug #32989)
When using Crystal Reports, table and column names would be truncated to 21 characters, and truncated columns in tables where the truncated name was the duplicated would lead to only a single column being displayed. (Bug #32864)
SQLFetchScroll() ignored the rowset size if
Don't cache result DSN option was set.
When using the ODBC
option, 'dirty' records would be read from tables as if the
option had not been applied.
When creating a System DSN using the ODBC Administrator on Mac OS X, a User DSN would be created instead. The root cause is a problem with the iODBC driver manager used on Mac OS X. The fix works around this issue.
ODBC Administrator may still be unable to register a System
DSN unless the
file has the correct permissions. You should ensure that the
file is writable by the
SQLFetchScroll would return negative data
lengths when using
SQLSetParam() caused memory allocation errors
due to driver manager's mapping of deprecated functions (buffer
Static cursor was unable to be used through ADO when dynamic cursors were enabled. (Bug #27351)
connection.Execute to create a record
set based on a table without declaring the cmd option as
adCmdTable will fail when communicating with
versions of MySQL 5.0.37 and higher. The issue is related to the
SQLSTATE is returned when ADO tries
to confirm the existence of the target object.
RecordSet when the query involves
BLOB field failed.
With some connections to MySQL databases using MySQL Connector/ODBC, the connection would mistakenly report 'user cancelled' for accesses to the database information. (Bug #16653)