It is now possible to specify a different character set as part of the DSN or connection string. This must be used instead of the
SET NAMESstatement. You can also configure the character set value from the GUI configuration. (Bug #9498, Bug #6667)
Fixed calling convention ptr and wrong free in myodbc3i, and fixed the null terminating (was only one, not two) when writing DSN to string.
Dis-allow NULL ptr for null indicator when calling SQLGetData() if value is null. Now returns SQL_ERROR w/state 22002.
The setup library has been split into its own RPM package, to enable installing the driver itself with no GUI dependencies.
myodbc3idid not correctly format driver info, which could cause the installation to fail. (Bug #29709)
Connector/ODBC crashed with Crystal Reports due to a problem with
SQLProcedures(). (Bug #28316)
Fixed a problem where the GUI would crash when configuring or removing a System or User DSN. (Bug #27315)
Fixed error handling of out-of-memory and bad connections in catalog functions. This might raise errors in code paths that had ignored them in the past. (Bug #26934)
For a stored procedure that returns multiple result sets, Connector/ODBC returned only the first result set. (Bug #16817)
RecNumber 0, DiagIdentifier NOT 0returned
SQL_ERROR, preventing access to diagnostic header fields. (Bug #16224)
Added a new DSN option (
FLAG_ZERO_DATE_TO_MIN) to retrieve
XXXX-00-00dates as the minimum permitted ODBC date (
XXXX-01-01). Added another option (
FLAG_MIN_DATE_TO_ZERO) to mirror this but for bound parameters.
0000-00-00. (Bug #13766)
If there was more than one unique key on a table, the correct fields were not used in handling
SQLSetPos(). (Bug #10563)
When inserting a large
BLOBfield, Connector/ODBC would crash due to a memory allocation error. (Bug #10562)
SQLColumns()did not handle many of its parameters correctly, which could lead to incorrect results. The table name argument was not handled as a pattern value, and most arguments were not escaped correctly when they contained nonalphanumeric characters. (Bug #8860)
There are no binary packages for Microsoft Windows x64 Edition.
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.
Correctly return error if
SQLBindColis called with an invalid column.
Fixed possible crash if
SQLBindCol()was not called before
The OS X binary packages are only provided as tarballs, there is no installer.
The binary packages for Sun Solaris are only provided as tarballs, not the PKG format.
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
Binary packages for Sun Solaris are now available as
Binary packages as disk images with installers are now available for OS X.
A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.