If the consumer completely releases and then refetches a row for which changes have been made by another rowset in the same transaction or by other applications operating outside the transaction, the visibility of these changes depends on the DBPROP_OTHERUPDATEDELETE and DBPROP_OTHERINSERT properties.
The visibility of changes made by other rowsets in the same transaction depends only on these properties. It does not depend on the transaction isolation level because the changes are in the same transaction.
The visibility of changes made by applications outside the current transaction depends on both the values of these properties and the transaction isolation level. The following table shows whether changes made by applications outside the current transaction are visible, depending on the transaction isolation level and the values of these properties.
Property value |
Read uncommitted |
Read committed |
Repeatable read |
Able to Serialize |
DBPROP_OTHERUPDATE- DELETE: VARIANT_TRUE VARIANT_FALSE |
Yes No |
Yes No |
No No |
No No |
DBPROP_OTHERINSERT: VARIANT_TRUE VARIANT_FALSE |
Yes No |
Yes No |
Yes No |
No No |