1
0
Fork 0
arangodb/Documentation/Books/Users/Transactions
Jan Steemann 4249095456 issue #1507: added optional *allowImplicit* sub-attribute for transactions 2015-09-24 15:50:00 +02:00
..
Durability.mdpp Some changes in the code documentation and fixed spelling errors 2014-06-26 15:54:29 +02:00
Limitations.mdpp updated docs 2014-07-04 13:53:24 +02:00
LockingAndIsolation.mdpp issue #1507: added optional *allowImplicit* sub-attribute for transactions 2015-09-24 15:50:00 +02:00
Passing.mdpp issue #970: Incorrect transaction example 2014-07-29 08:52:26 +02:00
README.mdpp updated docs 2014-07-04 13:53:24 +02:00
TransactionInvocation.mdpp issue #1507: added optional *allowImplicit* sub-attribute for transactions 2015-09-24 15:50:00 +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.