Neo4j is transactional, i.e. changes are isolated by an in-memory overlay per transaction (thread).
Only at commit the change becomes visible to other threads (isolation-level read-committed). The same is guaranteed for a cluster, which also adds causal consistency for read-your-own-writes using bookmarks. You can read more details about it in the free graph databases book and in the source code. On Mon, May 15, 2017 at 1:54 PM, <[email protected]> wrote: > Hi guys, > > I would like to understand(internals) how Neo4J is handling/implementing > ACID or transnational support for queries. > > Say i'm going through a complex graph traversal and how would Neo4J > provide query isolation for that traversal query? > > Please help me to understand these concepts. > > Thanks > - Mahi > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
