Informix Online Documentation |
Date: 09/27/99
Version: 2.1
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
The purpose of these release notes is to make you aware of any special actions required to configure and use Informix OLE DB Provider on your computer. This file also describes new features and feature differences from earlier versions of this product. In addition, this file contains information about known bugs and their workarounds.
This release notes document is not intended to be all-inclusive; it should be used as an addendum to the "Informix OLE DB Provider Programmer's Guide," which provides thorough information about product features and behavior.
These release notes are written for the following audience:
Client-side OLE DB Provider is compatible with the following Informix database servers:
Server-side OLE DB Provider is compatible with Informix Dynamic Server 2000, Version 9.2x (Windows NT).
Version 2.1 of Informix OLE DB Provider introduces the following features:
Applications can use ODBC command syntax as well as Informix command syntax to execute stored procedures. For example, the following command can be used with the ADO flag adCmdStoredProc:
{call foo(1, ?)}
In earlier versions of OLE DB Provider, if you specified a string type binding (DBTYPE_STR, DBTYPE_WSTR, or DBTPYPE_BSTR) when selecting an opaque type, the result was automatically printed in hexadecimal.
Working against the 9.2 server, OLE DB Provider 2.1 calls the server's output function to produce a text format that matches the output of DB-Access.
Earlier versions of OLE DB Provider checked the version of schema support on each connection attempt. OLE DB Provider 2.1 checks the version of schema support when schema rowsets are requested for the first time.
Earlier versions of OLE DB Provider could connect only to databases with the same GLS (Global Language Support) locale as DB_LOCALE.
OLE DB Provider 2.1 supports the DBPROP_PROVIDERSTRING parameters db_locale and client_locale, which the user can set (using the Setnet32 utility) to connect to databases with locales different from the DB_LOCALE setting.
For example, if DB_LOCALE and CLIENT_LOCALE are set to run ru_ru.0393, you can connect to a database with a en_us.1252 locale as follows (example uses VBScript):
The following conditions apply to these connections:
The default value of the autocommit isolation level in Informix OLE DB Provider is read-committed for databases created with logging and read-uncommitted for databases created without logging. In earlier versions of OLE DB Provider, this value could not be changed by the consumer, and the DBPROP_SESS_AUTOCOMMITISOLEVEL property was read-only. In OLE DB Provider 2.1, the DBPROP_SESS_AUTOCOMMITISOLEVEL property is read-write, and the consumer can set it for databases created with logging to read-uncommitted, read-committed, or serializable.
In earlier versions of OLE DB Provider, when the consumer specified the read-uncommitted isolation level for a local transaction, the transaction actually ran at the read-committed isolation level. OLE DB Provider 2.1 allows transactions to run at the read-uncommitted level.
When the isolation level is set to read-uncommitted for a database that has logging, data can be read from but not written to the database.
For information about resolving problems that you encounter while installing, configuring, or using OLE DB Provider, see "Resolving Problems" in the "Informix OLE DB Provider Programmer's Guide."
Storage objects created on string identifiers in schema rowsets now correctly reflect the object data type.
Problem: The Visual Basic Data Environment schema browser displayed incorrect table, column, and procedure names when it fetched data from schema rowsets.
Cause: The VB Data Environment schema browser fetches string-type data (such as schema names) as storage objects with a Unicode DBTYPE_WSTR binding. However, earlier versions of OLE DB Provider created these objects over MBCS (Multibyte Character Sequence) data.
Resolution: In OLE DB Provider 2.1,the storage objects are created over Unicode data rather than MBCS. The VB Data Environment schema browser now displays the correct schema names.