The ability to chain queries together allows for powerful constructs. In Cypher, the WITH clause is
used to pipe the result from one query to the next.
WITH is also used to separate reading from updating of the graph. Every sub-query of a query must be either read-only or write-only.
Graph
Aggregated results have to pass through a WITH clause to be able to filter on.
Query
START david=node(1) MATCH david--otherPerson-->() WITH otherPerson, count(*) as foaf WHERE foaf > 1 RETURN otherPerson
The person connected to David with the at least more than one outgoing relationship will be returned by the query.
Try this query live. (1) {"name":"David"} (2) {"name":"Emil"} (3) {"name":"Anders"} (4) {"name":"Bossman"} (5) {"name":"Cesar"} (1)-[:KNOWS]->(3) {} (3)-[:KNOWS]->(4) {} (3)-[:BLOCKS]->(5) {} (4)-[:KNOWS]->(2) {} (4)-[:BLOCKS]->(1) {} (5)-[:KNOWS]->(2) {} start david=node(1) match david--otherPerson-->() with otherPerson, count(*) as foaf where foaf > 1 return otherPerson
If you prefer a more visual way of writing your query, you can use equal-signs as delimiters before and after the column list. Use at least three before the column list, and at least three after.
Query
START david=node(1) MATCH david--otherPerson-->() ========== otherPerson, count(*) as foaf ========== SET otherPerson.connection_count = foaf
For persons connected to David, the connection_count property is set to their number of outgoing relationships.
Try this query live. (1) {"name":"David"} (2) {"name":"Emil"} (3) {"connection_count":2,"name":"Anders"} (4) {"connection_count":1,"name":"Bossman"} (5) {"name":"Cesar"} (1)-[:KNOWS]->(3) {} (3)-[:KNOWS]->(4) {} (3)-[:BLOCKS]->(5) {} (4)-[:KNOWS]->(2) {} (4)-[:BLOCKS]->(1) {} (5)-[:KNOWS]->(2) {} start david=node(1) match david--otherPerson-->() ========== otherPerson, count(*) as foaf ========== set otherPerson.connection_count = foaf