Consistent Transaction

A Consistent Transaction is a database transaction that must change affected data only in allowed ways including integrity constraints, cascading rollbacks, and database triggers.

• Context:
  • It can be a Consistent Atomic Transaction (also an atomic transaction).
  • It can be a Independent Atomic Transaction (also an independent transaction).
  • It can be a Durable Atomic Transaction (also a durable transaction).
  • …
• Counter-Example(s):
  • Atomic Transaction.
  • Independent Transaction.
  • Durable Transaction.
• See: Database Trigger, Database Systems, Database Transaction, Integrity Constraints, Cascading Rollback.

---

---

References

2020

• (Wikipedia, 2020) ⇒ https://en.wikipedia.org/wiki/consistency_(database_systems) Retrieved:2020-6-3.
  • Consistency in database systems refers to the requirement that any given database transaction must change affected data only in allowed ways. Any data written to the database must be valid according to all defined rules, including constraints, cascades, triggers, and any combination thereof. This does not guarantee correctness of the transaction in all ways the application programmer might have wanted (that is the responsibility of application-level code) but merely that any programming errors cannot result in the violation of any defined database constraints.

---