Managing Transactions and Threads
When you make changes to a repository database, the updates are done within the scope of a transaction. You use repository transaction management methods to ensure that changes to a repository database always leave the database in a consistent state. This section discusses the transaction management support provided by the repository engine, and the threading model that is supported by repository objects.
Knowing how to perform a transaction is necessary if you are creating or extending information models programmatically, or writing programs that populate or update an information model.
Transactions are not required for programming to retrieve data through the repository engine.
The following topics provide more information about transactions.
| Topic | Description |
|---|---|
| Transaction Management Overview | Explains when you should use a transaction and how transactions are implemented by the repository engine. |
| Design Issues and Transaction Management | Describes design issues that you should consider when implementing transaction behavior in an application. |
| Repository Objects and Multithreading | Explains transaction behavior and issues that apply when running multiple instances of a repository. |
See Also
IRepositoryTransaction Interface