Skip navigation links
MySQL 5.1 Reference Manual :: C MySQL Change History :: C.3 MySQL Connector/ODBC (MyODBC) Change History :: C.3.20 Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)
C.3.21 Changes in MySQL Connector/ODBC 3.51.27 (20 November 2008) »
Section Navigation      [Toggle]

C.3.20. Changes in MySQL Connector/ODBC 3.51.28 (Not yet released)

Bugs fixed:

  • 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)

  • 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)