Nested transaction

A nested transaction is a database transaction that is started by an instruction within the scope of an already started transaction.

Nested transactions are implemented differently in different databases. However, they have in common that the changes are not made visible to any unrelated transactions until the outermost transaction has committed. This means that a commit in an inner transaction does not necessarily persist updates to the system.

In some databases, changes made by the nested transaction are not seen by the 'host' transaction until the nested transaction is committed. According to some, this follows from the isolation property of transactions.

The capability to handle nested transactions properly is a prerequisite for true component-based application architectures. In a component-based encapsulated architecture, nested transactions can occur without the programmer knowing it. A component function may or may not contain a database transaction (this is the encapsulated secret of the component. See Information hiding). If a call to such a component function is made inside a BEGIN - COMMIT bracket, nested transactions occur. Since popular databases like MySQL[1] do not allow nesting BEGIN - COMMIT brackets, a framework or a transaction monitor is needed to handle this. When we speak about nested transactions, it should be made clear that this feature is DBMS dependent and is not available for all databases.

Theory for nested transactions is similar to the theory for flat transactions.[2]

The banking industry usually processes financial transactions using open nested transactions, which is a looser variant of the nested transaction model that provides higher performance while accepting the accompanying trade-offs of inconsistency.[3]

Further reading
  • Gerhard Weikum, Gottfried Vossen, Transactional information systems: theory, algorithms, and the practice of concurrency control and recovery, Morgan Kaufmann, 2002, ISBN 1-55860-508-8
gollark: If you think people have a 0.02% chance of dying of COVID-19, and I arbitrarily assume you think young people are 1 OOM better off (so 0.002% chance), then that's still better than the maybe 0.0001% (1 in 1 million) chance of dying of vaccines.
gollark: You can do multiple things, actually.
gollark: In which case that's... substantially more than 1 per million.
gollark: I assume you mean 0.02%.
gollark: That would be very worrying.

References
  1. "Statements That Cause an Implicit Commit". MySQL 4.1 Reference Manual. Oracle. Retrieved 5 December 2010.
  2. Resende, R.F.; El Abbadi, A. (1994-05-25). "On the serializability theorem for nested transactions". Information Processing Letters. 50 (4): 177–183. CiteSeerX 10.1.1.43.6470. doi:10.1016/0020-0190(94)00033-6.
  3. Weikum, Gerhard; Hans-J. Schek (1992). Concepts and Applications of Multilevel Transactions and Open Nested Transactions. Database Transaction Models for Advanced Applications. Morgan Kaufmann. pp. 515–553. CiteSeerX 10.1.1.17.7962. ISBN 978-1-55860-214-4.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.