The new connection option
indicates that your application includes error-handling logic to
deal with the error code for an expired password. See
Connector/ODBC Connection Parameters
for the details of this connection option and the associated SQL
state and native error code. See ALTER USER Syntax
for details about password expiration for MySQL server accounts.
This new option is added to the Windows GUI, through a checkbox Can Handle Expired Password on the Connection tab of the Details dialog.
The following reserved words were added to the list returned by
SQLGetInfo() ODBC function, for
compatibility with the latest MySQL 5.6 syntax:
The string returned by the
function was not null-terminated as it should be.
Specifying certain values for the
option in the connection string could cause a serious error when
a query was executed.
If multiple statements were called using the same statement
SQLColumns and possibly other catalog
functions could return wrong results. Some field length values
were not reset in the descriptor records. The issue occurred
even if the statement handle was closed with
SQL_CLOSE between the statements.
If an application received a
SIGPIPE signal immediately after
(before the first signal handler was finished), the application
could terminate rather than handling the second signal.
Several catalog or info functions could raise an incorrect error
String data, right truncated when only
partial information was requested. For example, if the
called SQLDescribeCol(hstmt, ColNumber,
ColName, BufferLen, ....), but did not want the column
ColName == NULL and
also be returned rather than the correct value
SQL_SUCCESS. This issue affected many ADO,
DAO, and other applications.
Affected functions include:
Spurious error and incorrect return code: SQLDescribeCol SQLDescribeColA SQLDescribeColW SQLGetInfoA SQLGetInfoW Incorrect return code: SQLColAttribute SQLColAttributeW SQLGetConnectAttr SQLGetConnectAttrW SQLGetCursorName SQLGetCursorNameW SQLGetInfo SQLGetInfoW SQLNativeSql SQLNativeSqlW
SQLTables function with a very
long database or table name could cause a serious error. This
fix allows the
SQLTables function to accept
database and table names with the maximum length of 64
SQLRemoveDriverW were exported, causing
incompatibility with some commercial ODBC packages such as
DataDirect ODBC, and making Connector/ODBC dependent on the
libodbcinst.so.1. This issue was first
observed in Connector/ODBC 5.1.8.
(Bug #11766724, Bug #59900)
On a 64-bit system, calls to the
function using indicator variables (through the last parameter)
could return incorrect results.
(Bug #11766437, Bug #59541)
When a column with type
LONGTEXT was retrieved from a
table with a binary collation, the text fields were converted to
a hexadecimal representation, even though these values were not
really BLOBs. The unnecessary conversion could expand the data,
causing overflow problems when storing the result values.
(Bug #11746572, Bug #27282)