1
0
Fork 0
arangodb/Documentation/Books/Manual/Transactions
Wilfried Goesgens b8e55ef022 fix https://github.com/arangodb/arangojs/issues/508 (#4664) 2018-02-27 14:54:51 +01:00
..
Durability.md rename .mdpp files to .md so the handling is easier. 2017-05-04 12:04:24 +02:00
Limitations.md Doc - Adds toc plugin (#4577) 2018-02-13 19:04:32 +01:00
LockingAndIsolation.md Doc - Adds toc plugin (#4577) 2018-02-13 19:04:32 +01: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 fix https://github.com/arangodb/arangojs/issues/508 (#4664) 2018-02-27 14:54:51 +01: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.