The new connection option
can_handle_exp_pwdindicates 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 the
SQLGetInfo()ODBC function, for compatibility with the latest MySQL 5.6 syntax:
The string returned by the
SQLNativeSqlfunction was not null-terminated as it should be. (Bug #14559721)
Specifying certain values for the
CHARSEToption in the connection string could cause a serious error when a query was executed. (Bug #14363601)
If multiple statements were called using the same statement handle,
SQLColumnsand 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_CLOSEbetween the statements. (Bug #14338051)
If an application received a
SIGPIPEsignal, then another
SIGPIPEsignal immediately after (before the first signal handler was finished), the application could terminate rather than handling the second signal. (Bug #14303803)
Several catalog or info functions could raise an incorrect error
String data, right truncatedwhen only partial information was requested. For example, if the application
called SQLDescribeCol(hstmt, ColNumber, ColName, BufferLen, ....), but did not want the column name (
ColName == NULLand
BufferLen == 0).
SQL_SUCCESS_WITH_INFOcould 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
SQLTablesfunction with a very long database or table name could cause a serious error. This fix allows the
SQLTablesfunction to accept database and table names with the maximum length of 64 characters. (Bug #14085211)
SQLRemoveDriverWwere 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
SQLBindColfunction using indicator variables (through the last parameter) could return incorrect results. (Bug #11766437, Bug #59541)
When a column with type
LONGTEXTwas 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)