com.tinkerpop.blueprints

Interface TransactionalGraph

All Superinterfaces:

Graph

All Known Subinterfaces:

ThreadedTransactionalGraph

All Known Implementing Classes:

BatchGraph, EventTransactionalGraph, EventTransactionalIndexableGraph, IdGraph

public interface TransactionalGraph
extends Graph

A transactional graph supports the notion of transactions. A transaction scopes a logically coherent operation composed of multiple read and write operations that either occurs at once or not at all. The exact notion of a transaction and its isolational guarantees depend on the implementing graph database. A transaction scopes a coherent and complete operations. Any element references created during a transaction should not be accessed outside its scope (i.e. after the transaction is committed or rolled back). Accessing such references outside the transactional context they were created in may lead to exceptions. If such access is necessary, the transactional context should be extended. By default, the first operation on a TransactionalGraph will start a transaction automatically.

Author:

Matthias Broecheler (http://matthiasb.com), Marko A. Rodriguez (http://markorodriguez.com)

Nested Class Summary

Nested Classes

Modifier and Type	Interface and Description
static class	TransactionalGraph.Conclusion Deprecated.

Method Summary

Methods

Modifier and Type	Method and Description
void	commit() Stop the current transaction and successfully apply mutations to the graph.
void	rollback() Stop the current transaction and drop any mutations applied since the last transaction.
void	stopTransaction(TransactionalGraph.Conclusion conclusion) Deprecated.

Methods inherited from interface com.tinkerpop.blueprints.Graph

addEdge, addVertex, getEdge, getEdges, getEdges, getFeatures, getVertex, getVertices, getVertices, query, removeEdge, removeVertex, shutdown

Method Detail

stopTransaction

@Deprecated
void stopTransaction(TransactionalGraph.Conclusion conclusion)

Deprecated.

Stop the current transaction. Specify whether the transaction was successful or not. A failing transaction will rollback all updates to before the transaction was started. If there is currently no open transaction (i.e. no operations on the graph), then calling this method has no effect other than potentially re-initializing data structures.

Parameters:

conclusion - whether or not the current transaction was successful

commit

void commit()

Stop the current transaction and successfully apply mutations to the graph.

rollback

void rollback()

Stop the current transaction and drop any mutations applied since the last transaction.