1
0
Fork 0
arangodb/Documentation/Books/Manual/Transactions
Dan Larkin 9b53d3cd45 Documented custom exception behavior (addresses issue #2561). (#2595) 2017-06-18 22:50:01 +02:00
..
Durability.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
Limitations.md updated documentation 2017-05-31 11:33:57 +02:00
LockingAndIsolation.md added documentation 2017-05-30 16:39:40 +02:00
Passing.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
README.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
TransactionInvocation.md Documented custom exception behavior (addresses issue #2561). (#2595) 2017-06-18 22:50:01 +02:00

README.md

Transactions

Starting with version 1.3, ArangoDB provides support for user-definable transactions.

Transactions in ArangoDB are atomic, consistent, isolated, and durable (ACID).

These ACID properties provide the following guarantees:

  • The atomicity principle makes transactions either complete in their entirety or have no effect at all.
  • The consistency principle ensures that no constraints or other invariants will be violated during or after any transaction.
  • The isolation property will hide the modifications of a transaction from other transactions until the transaction commits.
  • Finally, the durability proposition makes sure that operations from transactions that have committed will be made persistent. The amount of transaction durability is configurable in ArangoDB, as is the durability on collection level.