TransactionStatus uses ConstantsTrait
Lifecycle states of a streaming transaction, reported by the ArangoDB server in the `status` field of `/_api/transaction/{id}` responses.
A streaming transaction starts in RUNNING when Database::beginTransaction() returns. It then moves to either COMMITTED (every step is durably applied) or ABORTED (every step is discarded). Both terminal states are final — once a transaction is committed or aborted, it cannot be reused; the caller has to start a fresh one.
The server also auto-aborts a transaction that stays idle longer than its configured TTL, so a client that crashes or disconnects mid-flight does not leak transactional locks indefinitely.
Tags
Table of Contents
Constants
- ABORTED : string = 'aborted'
- The transaction has been aborted (explicitly or by the server after an idle timeout). All staged writes have been discarded.
- COMMITTED : string = 'committed'
- The transaction has been committed. All staged writes are durably applied.
- RUNNING : string = 'running'
- The transaction is open and accepts further steps.
Constants
ABORTED
The transaction has been aborted (explicitly or by the server after an idle timeout). All staged writes have been discarded.
public
string
ABORTED
= 'aborted'
COMMITTED
The transaction has been committed. All staged writes are durably applied.
public
string
COMMITTED
= 'committed'
RUNNING
The transaction is open and accepts further steps.
public
string
RUNNING
= 'running'