I have failed to resolve this and have raised a question over on
SO:
http://stackoverflow.com/questions/25603163/neo4j-cypher-merge-query-isolation-level
M
On Friday, 29 August 2014 19:56:14 UTC+1, Mark Findlater wrote:
>
> I understand, and I have corrected that. Unfortunately I still have the
I understand, and I have corrected that. Unfortunately I still have the
issue, but if this is feature complete I will work on it some more and
failing to find a solution I will ask the question over on SO. For
completeness my Index is created like this:
CREATE CONSTRAINT ON (n:`UniqueId`) ASSE
Currently your merge op uses two labels :UniqueId and :_UniqueId
Merge only supports guarantees for one label one prop
You can set the secon label in on create
Sent from mobile device
Am 29.08.2014 um 16:30 schrieb Mark Findlater :
> Thanks Michael.
>
> Sorry I should have been more clear, th
Thanks Michael.
Sorry I should have been more clear, there is already a Unique constraint
on the 'type' property. What do you mean by "And only the label from the
constraint"?
On Friday, 29 August 2014 15:25:35 UTC+1, Michael Hunger wrote:
>
> You need a unique constraint for this to work
>
>
You need a unique constraint for this to work
And only the label from the constraint
Sent from mobile device
Am 29.08.2014 um 15:36 schrieb Mark Findlater :
> Using Neo4J embedded version 2.1.3 and Spring Data Neo4J 3.1.4.RELEASE and
> seeing odd behaviour when calling MERGE from multiple th
Using Neo4J embedded version 2.1.3 and Spring Data Neo4J 3.1.4.RELEASE and
seeing odd behaviour when calling MERGE from multiple threads. Is it
expected that concurrent merge operations (with the same values) will
result in a single unique node and will operations that use the ON CREATE
and ON
