1
0
Fork 0
arangodb/Documentation/Books/Manual/Transactions
Simran Brucherseifer 0bcd75921f Docs: Fix locking and isolation code examples (require db object and use AQL traversal) 2016-07-25 18:43:30 +02:00
..
Durability.mdpp Rename Users documentation to Manual 2016-05-24 16:09:21 +02:00
Limitations.mdpp Rename Users documentation to Manual 2016-05-24 16:09:21 +02:00
LockingAndIsolation.mdpp Docs: Fix locking and isolation code examples (require db object and use AQL traversal) 2016-07-25 18:43:30 +02:00
Passing.mdpp Rename Users documentation to Manual 2016-05-24 16:09:21 +02:00
README.mdpp Rename Users documentation to Manual 2016-05-24 16:09:21 +02:00
TransactionInvocation.mdpp replaced require("internal").db by require("@arangodb").db 2016-07-22 16:22:23 +02:00

README.mdpp

!CHAPTER 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.