Thanks, Michael. I'm using an embedded graph database with the java api.
I think I fixed it with the "synchronized" key word on the method.
On Wed, Jun 15, 2016 at 8:53 PM, 'Michael Hunger' via Neo4j <
neo4j@googlegroups.com> wrote:
> You have to create a lock to make that an exclusive operation
You have to create a lock to make that an exclusive operation.
Best with cypher's MERGE and a unique constraint which take care of
creating that index lock for you:
create constraint on t:Top assert t.id is unique;
MERGE (t:Top {id:123}) RETURN t;
On Wed, Jun 15, 2016 at 12:27 AM, David Starkw
Hell all,
Thanks for all your hard work in delivering such a great product.
I have an application built on top of neo4j using the java api for v3.0.1.
It requires finding a "top" node first at the beginning of every one of my
graph operations. This top node serves as the start of my graph db
