In neo4j-browser you need type for example: :params {nodes: [{name: “John”, age: 18}, {name: “Phill”, age: 23}]} Then you can use params as usual: UNWIND {nodes} as node MERGE (A:User {name: node.name, age: node.age}) RETURN A For clear params in neo4j-browser type :params {}. For additional help type :help params.
CREATE UNIQUE has slightly more obscure semantics than MERGE. MERGE was developed as an alternative with more intuitive behavior than CREATE UNIQUE; if in doubt, MERGE is usually the right choice. The easiest way to think of MERGE is as a MATCH-or-create. That is, if something in the database would MATCH the pattern you are … Read more
Your matching by label is incorrect, the query should be: MATCH (n:User) SET n.surname=”Taylor” RETURN n What you wrote is: “match a user whose label property is User”. Label isn’t a property, this is a notion apart. As Michael mentioned, if you want to match a node with a specific property, you’ve got two alternatives: … Read more
neo4j (2.0.1) does not currently support a uniqueness constraint that covers multiple properties simultaneously. However, I can think of a workaround that might be acceptable, depending on your use cases. Let’s say you want properties a, b, and c to be unique as a group. You can add an extra property, d, that concatenates the … Read more
This should do it: MATCH (n) WHERE NOT n:Label1 AND NOT n:Label2 RETURN n;
Adding values to an array is analogous to incrementing an integer or concatenating a string and is signified the same way, in your case (let c be your [c:contains {id:[12345]}]) c.id = c.id + 1111 // [12345,1111] c.id = c.id + 14567 // [12345,1111,14567] or c.id = c.id + [1111,14567] // [12345,1111,14567]
You can’t do this in Cypher yet. I think it would be a nice feature though, if you want to request it. Edit (thanks for comment pointing it out): You can now do this as of 2.2: MATCH (p:Product) WHERE p.price=”1950″ RETURN keys(p);
MATCH (n:OLD_LABEL {id:14}) REMOVE n:OLD_LABEL SET n:NEW_LABEL Guess this query explains itself.
Unfortunately there is no direct change of rel-type possible at the moment. You can do: MATCH (n:User {name:”foo”})-[r:REL]->(m:User {name:”bar”}) CREATE (n)-[r2:NEWREL]->(m) // copy properties, if necessary SET r2 = r WITH r DELETE r
The browser is telling you that: It is handling your query by doing a comparison between every Gene instance and every Chromosome instance. If your DB has G genes and C chromosomes, then the complexity of the query is O(GC). For instance, if we are working with the human genome, there are 46 chromosomes and … Read more