Re: [Neo4j] Slow node creation/commits with unique constraint in 2.0.0

I meant: with an index you the fast lookup but no pentalty with an constraint you have the uniqueness guarantee via a lock and check against the constraint on write, both of which cost. But I ask if that can be alleviated. Could you test it in 3.0.2 if it performs better? Michael > Am

Re: [Neo4j] Re: Slow node creation/commits with unique constraint in 2.0.0

I'm sorry, I'm not sure exactly what you mean by query scan. I haven't changed any of the queries from before the addition of the uniqueness constraint. I'm still doing the same "MERGE ..." query (like above, but with parameters, as you pointed out). Do you mean that, or something else?

Re: [Neo4j] Re: Slow node creation/commits with unique constraint in 2.0.0

Can you share the query plan from before and after the constraint? Oh if you had an index on uid then you had the benefit of the "fast scan" but without the penalty of "asserting uniqueness across the index". Michael > Am 26.05.2016 um 18:25 schrieb Eric Fulton : > >

[Neo4j] Go through all the transitive relationships in the database

I am trying to find an efficient way of traversing all nodes and find transitive relationships of length 2 on my database. Currently, I am using query1 to compute the new properties for the new relationship and query 2 to add the relationship into the database query1: MATCH (a:USERS) -

Re: [Neo4j] Visuaization Tool for Neo4J

Thankyou everyone for the help! -Sukaant Chaudhary On Sun, May 22, 2016 at 9:24 PM, 'Michael Hunger' via Neo4j < neo4j@googlegroups.com> wrote: > Max De Marzi has a ton of write-ups on Data Visualization: >

Re: [Neo4j] Re: Slow node creation/commits with unique constraint in 2.0.0

So before the constraint, I was still using merges because I really did want something akin to uniqueness for these nodes. We had an index on the "uid" so maybe that helped with the full scan? Yes, I use parameters, not literal values. -- You received this message because you are subscribed

Re: [Neo4j] Guide needed for implementation of my use case

Hi Reeika, You can access the property key as follows query: MATCH(n:PERSON{name:blah1,Pnumber:blah2, status:Cancelled/Not Cancelled}) Return count(n.status) See if this works ᐧ Regards, Yayati Sule Associate Data Scientist Innoplexus Consulting Services Pvt. Ltd. www.innoplexus.com

Re: [Neo4j] Cypher queries in python

Hi Jessica, when you execute the query cypher query, just iterate over the cursor and append it to a list. Then using the json.dumps() method you can get the result in JSON format. You may then analyze it as per your needs ᐧ Regards, Yayati Sule Associate Data Scientist Innoplexus Consulting

[Neo4j] Guide needed for implementation of my use case

Hi all experts out there, I am looking for a solution using neo4j for my use case where in I want to calculate the churn for a Telecom Company. I am a student and very new to nosql. I tried this Node Label: Customer Properties: Name, own phone number and contract Status: cancelled or not

[Neo4j] Cypher queries in python

I'm migrating a postgresql database to neo4J. I am using the Python language, but I have a problem. I have a table called 'historico' which marks the rainfall recorded by a sensor in a certain latitude and longitude. My problem is the following: if a node with such latitude and longitude in my