Telerik OpenAccess Classic

Telerik OpenAccess ORM Send comments on this topic.
Programmer's Guide > OpenAccess ORM Classic (Old API) > Programming With OpenAccess > Transactions

Glossary Item Box

This documentation article is a legacy resource describing the functionality of the deprecated OpenAccess Classic only. The contemporary documentation of Telerik OpenAccess ORM is available here.

A transaction is an indivisible unit of work and it is used to ensure data integrity. Transactions control the concurrent access of data by multiple programs. In the event of a system failure, transactions ensure that after recovery the data is in a consistent state. All operations on a persistent class need to be carried out within a transaction. Transactions are started with Transaction.Begin(), following this you can do whatever operations are needed. A transaction can end in two ways: with a commit or a rollback. Transaction.Commit() attempts to save all the changes to the database, however, if any statement within the transaction fails, the transaction is rolled back, undoing all the effects of the statements in the transaction.

This chapter examines the working of transactions in OpenAccess ORM in detail and it includes the following sections:


Transaction Principles (ACID properties)


OpenAccess ORM Transaction API


Multi-threaded Applications


Concurrency control


Transaction properties