Partager via

  • Article

ITransaction

Topic Last Modified: 2006-06-11

The Exchange OLE DB provider provides an implementation of the ITransactionLocal interface with the following restrictions:

  • Nested transactions are not supported.
  • The ITransactionJoin interface, used to perform two-phase commit transactions, is not supported.
  • Full transaction isolation is not supported. The provider prevents dirty reads (in other words, supported by grouped operations), yet allows non-repeatable reads or phantoms. Specifically, the provider allows read committed (that is, cursor stability). This means that the provider will only support a value of ISOLATION_LEVEL_READCOMMITTED for the isoLevel argument of ITransactionLocal::StartTransaction. All other values specified for the isoLevel parameter will cause ITransactionLocal::StartTransaction to fail with an error reporting that this isolation level is not a valid option.