Changes in MySQL Connector/ODBC 5.1.1 (2007-12-13, Beta)

MySQL Connector/ODBC 5.1.1-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the first beta (feature-complete) release of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)

Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.

Includes changes from Connector/ODBC 3.51.21 and 3.51.22.

Built using MySQL 5.0.52.

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• Incompatible Change: Replaced myodbc3i (now myodbc-installer) with Connector/ODBC 5.0 version.

• Incompatible Change: Removed monitor (myodbc3m) and dsn-editor (myodbc3c).

• Incompatible Change: Do not permit SET NAMES in initial statement and in executed statements.

• A wrapper for the SQLGetPrivateProfileStringW() function, which is required for Unicode support, has been created. This function is missing from the unixODBC driver manager. (Bug #32685)

• Added MSI installer for Windows 64-bit. (Bug #31510)

• Implemented support for SQLCancel(). (Bug #15601)

• Added support for SQL_NUMERIC_STRUCT. (Bug #3028, Bug #24920)

• Removed nonthreadsafe configuration of the driver. The driver is now always built against the threadsafe version of libmysql.

• Implemented native Windows setup library

• Replaced the internal library which handles creation and loading of DSN information. The new library, which was originally a part of Connector/ODBC 5.0, supports Unicode option values.

• The Windows installer now places files in a subdirectory of the Program Files directory instead of the Windows system directory.

Bugs Fixed

• The SET NAMES statement has been disabled because it causes problems in the ODBC driver when determining the current client character set. (Bug #32596)

• SQLDescribeColW returned UTF-8 column as SQL_VARCHAR instead of SQL_WVARCHAR. (Bug #32161)

• ADO was unable to open record set using dynamic cursor. (Bug #32014)

• ADO applications would not open a RecordSet that contained a DECIMAL field. (Bug #31720)

• Memory usage would increase considerably. (Bug #31115)

• SQL statements are limited to 64KB. (Bug #30983, Bug #30984)

• SQLSetPos with SQL_DELETE advances dynamic cursor incorrectly. (Bug #29765)

• Using an ODBC prepared statement with bound columns would produce an empty result set when called immediately after inserting a row into a table. (Bug #29239)

• ADO Not possible to update a client side cursor. (Bug #27961)

• Recordset Update() fails when using adUseClient cursor. (Bug #26985)

• Connector/ODBC failed to connect to the server if the password contained certain characters, including the semicolon and other punctuation marks. (Bug #16178)

• The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.

• There is no binary package for OS X on 64-bit PowerPC because Apple does not currently provide a 64-bit PowerPC version of iODBC.

• The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.

• Fixed SQL_ATTR_PARAM_BIND_OFFSET, and fixed row offsets to work with updatable cursors.

• SQLSetConnectAttr() did not clear previous errors, possibly confusing SQLError().

• SQLError() incorrectly cleared the error information, making it unavailable from subsequent calls to SQLGetDiagRec().

• NULL pointers passed to SQLGetInfo() could result in a crash.

• SQL_ODBC_SQL_CONFORMANCE was not handled by SQLGetInfo().

• SQLCopyDesc() did not correctly copy all records.

• Diagnostics were not correctly cleared on connection and environment handles.

• Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that you uninstall any existing versions of Connector/ODBC 5.1.x before upgrading.

  References: See also: Bug #34571.