Changes in MySQL Connector/ODBC 5.2.4 (5 February, 2013)
This release fixes any bugs encountered since Connector/ODBC
5.2.3. Its main focus is on compatibility with the latest features
of MySQL 5.6.
Functionality Added or Changed
* The new connection option can_handle_exp_pwd indicates that
your application includes error-handling logic to deal with
the error code for an expired password. See Connector/ODBC
Connection Parameters
(http://dev.mysql.com/doc/refman/5.5/en/connector-odbc-configu
ration-connection-parameters.html) for the details of this
connection option and the associated SQL state and native
error code. See ALTER USER Syntax
(http://dev.mysql.com/doc/refman/5.6/en/alter-user.html) 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:
+ GET
+ IO_AFTER_GTIDS
+ IO_BEFORE_GTIDS
+ MASTER_BIND
+ ONE_SHOT
+ PARTITION
+ SQL_AFTER_GTIDS
+ SQL_BEFORE_GTIDS
Bugs Fixed
* When a column with type TINYTEXT, TEXT, MEDIUMTEXT, or
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)
| Subject | Views | Written By | Posted |
|---|---|---|---|
| MySQL Connector/ODBC 5.2.4 has been released | 1185 | Kent Boortz | 02/05/2013 07:45AM |
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.