Documentation Home
MySQL Connector/ODBC Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 245.2Kb
PDF (A4) - 244.1Kb
EPUB - 61.2Kb

MySQL Connector/ODBC Release Notes  /  Changes in MySQL Connector/ODBC Version 3.51  /  Changes in MySQL Connector/ODBC 3.51.28 (2011-02-09)

Changes in MySQL Connector/ODBC 3.51.28 (2011-02-09)

Bugs Fixed

  • SQLColAttribute(...SQL_DESC_CASE_SENSITIVE...) returned SQL_FALSE for binary types and SQL_TRUE for the rest. It should have returned SQL_TRUE for binary types, and SQL_FALSE for the rest. (Bug #54212)

  • SQLColAttribute for SQL_DESC_OCTET_LENGTH returned length including terminating null byte. It should not have included the null byte. (Bug #54206)

  • If NO_BACKSLASH_ESCAPES mode was used on a server, escaping binary data led to server query parsing errors. (Bug #49029)

  • Inserting a new record using SQLSetPos did not correspond to the database name specified in the SELECT statement when querying tables from databases other than the current one.

    SQLSetPos attempted to do the INSERT in the current database, but finished with a SQL_ERROR result and Table does not exist message from MySQL Server. (Bug #41946)

  • When using MySQL Connector/ODBC to fetch data, if a net_write_timeout condition occurred, the operation returned the standard "end of data" status, rather than an error. (Bug #39878)

  • No result record was returned for SQLGetTypeInfo for the TIMESTAMP data type. An application would receive the result return code 100 (SQL_NO_DATA_FOUND). (Bug #30626)

  • Microsoft Access was not able to read BIGINT values properly from a table with just two columns of type BIGINT and VARCHAR. #DELETE appeared instead of the correct values. (Bug #17679)

Download these Release Notes
PDF (US Ltr) - 245.2Kb
PDF (A4) - 244.1Kb
EPUB - 61.2Kb