2017-04-12 19:30:09 +03:00
---
2024-10-21 00:46:35 +03:00
language: Cypher
2017-04-12 19:30:09 +03:00
filename: LearnCypher.cql
contributors:
- ["Théo Gauchoux", "https://github.com/TheoGauchoux"]
---
2024-04-20 19:05:03 +03:00
Cypher is Neo4j's query language for easily manipulating graphs.
It reuses syntax from SQL and mixes it with kind of an ASCII-art to represent graphs.
2017-04-12 19:30:09 +03:00
This tutorial assumes that you already know graph concepts like nodes and relationships.
2024-04-20 19:05:03 +03:00
## Nodes represent a record in a graph
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`()` is an empty *node* , to indicate that there is a *node* , but it's not relevant for the query.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(n)` is a *node* referred by the variable `n` , reusable in the query. It begins with lowercase and uses camelCase.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(p:Person)` - you can add a *label* to your node, here `Person` . It's like a type/class/category. It begins with uppercase and uses camelCase.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(p:Person:Manager)` - a node can have many *labels* .
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(p:Person {name : 'Théo Gauchoux', age : 22})` - a node can have some *properties* , here `name` and `age` . It begins with lowercase and uses camelCase.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
The types allowed in properties:
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
- Numeric
- Boolean
- String
- List of previous primitive types
2017-04-13 18:21:23 +03:00
2024-04-20 19:05:03 +03:00
*Warning: there's no datetime properties in Cypher! You can use a String with a specific pattern or a Numeric from a specific date.*
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`p.name` - you can access a property with the dot style.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
## Relationships (or Edges) connect two nodes
2017-04-12 19:30:09 +03:00
2024-05-15 05:05:35 +03:00
`[:KNOWS]` is a *relationship* with the *label* `KNOWS` . It's a *label* as the node's label. It uses UPPER\_SNAKE\_CASE.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`[k:KNOWS]` - the same *relationship* , referred by the variable `k` , reusable in the query, but it's not necessary.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`[k:KNOWS {since:2017}]` - the same *relationship* , with *properties* (like *node* ), here `since` .
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`[k:KNOWS*..4]` is structural information to use in a *path* (seen later). Here, `\*..4` says "Match the pattern, with the relationship `k` which can be repeated between 1 and 4 times.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
## Paths - the way to mix nodes and relationships.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(a:Person)-[:KNOWS]-(b:Person)` - a path describing that `a` and `b` know each other.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(a:Person)-[:MANAGES]->(b:Person)` - a path can be directed. This path describes that `a` is the manager of `b` .
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(a:Person)-[:KNOWS]-(b:Person)-[:KNOWS]-(c:Person)` - you can chain multiple relationships. This path describes the friend of a friend.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`(a:Person)-[:MANAGES]->(b:Person)-[:MANAGES]->(c:Person)` - a chain can also be directed. This path describes that `a` is the boss of `b` and the big boss of `c` .
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
Commonly used patterns (from Neo4j documentation):
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
```cypher
// Friend-of-a-friend
2017-04-12 19:30:09 +03:00
(user)-[:KNOWS]-(friend)-[:KNOWS]-(foaf)
// Shortest path
path = shortestPath( (user)-[:KNOWS*..5]-(other) )
// Collaborative filtering
(user)-[:PURCHASED]->(product)< - [ :PURCHASED ] - ( ) - [ :PURCHASED ] - > (otherProduct)
2024-04-20 19:05:03 +03:00
// Tree navigation
2017-04-12 19:30:09 +03:00
(root)< - [ :PARENT * ] - ( leaf:Category ) - [ :ITEM ] - > (data:Product)
```
2024-04-20 19:05:03 +03:00
## Create queries
2017-04-12 19:30:09 +03:00
Create a new node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
CREATE (a:Person {name:"Théo Gauchoux"})
RETURN a
```
2024-04-06 18:33:50 +03:00
2017-04-12 19:30:09 +03:00
*`RETURN` allows to have a result after the query. It can be multiple, as `RETURN a, b` .*
Create a new relationship (with 2 new nodes)
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
CREATE (a:Person)-[k:KNOWS]-(b:Person)
RETURN a,k,b
```
2024-04-20 19:05:03 +03:00
## Match queries
2017-04-12 19:30:09 +03:00
Match all nodes
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (n)
RETURN n
```
Match nodes by label
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (a:Person)
RETURN a
```
Match nodes by label and property
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (a:Person {name:"Théo Gauchoux"})
RETURN a
```
Match nodes according to relationships (undirected)
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (a)-[:KNOWS]-(b)
RETURN a,b
```
Match nodes according to relationships (directed)
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (a)-[:MANAGES]->(b)
RETURN a,b
```
Match nodes with a `WHERE` clause
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person {name:"Théo Gauchoux"})-[s:LIVES_IN]->(city:City)
WHERE s.since = 2015
RETURN p,state
```
You can use `MATCH WHERE` clause with `CREATE` clause
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (a), (b)
WHERE a.name = "Jacquie" AND b.name = "Michel"
CREATE (a)-[:KNOWS]-(b)
```
2024-04-20 19:05:03 +03:00
## Update queries
2017-04-12 19:30:09 +03:00
Update a specific property of a node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)
WHERE p.name = "Théo Gauchoux"
SET p.age = 23
```
Replace all properties of a node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)
WHERE p.name = "Théo Gauchoux"
SET p = {name: "Michel", age: 23}
```
Add new property to a node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)
WHERE p.name = "Théo Gauchoux"
2024-04-20 19:05:03 +03:00
SET p += {studies: "IT Engineering"}
2017-04-12 19:30:09 +03:00
```
Add a label to a node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)
WHERE p.name = "Théo Gauchoux"
SET p:Internship
```
2024-04-20 19:05:03 +03:00
## Delete queries
2017-04-12 19:30:09 +03:00
Delete a specific node (linked relationships must be deleted before)
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)-[relationship]-()
WHERE p.name = "Théo Gauchoux"
DELETE relationship, p
```
Remove a property in a specific node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)
WHERE p.name = "Théo Gauchoux"
REMOVE p.age
```
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
*Pay attention to the `REMOVE` keyword, it's not `DELETE` !*
2017-04-12 19:30:09 +03:00
Remove a label from a specific node
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (p:Person)
WHERE p.name = "Théo Gauchoux"
DELETE p:Person
```
Delete entire database
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
```cypher
2017-04-12 19:30:09 +03:00
MATCH (n)
OPTIONAL MATCH (n)-[r]-()
DELETE n, r
```
2024-04-06 18:33:50 +03:00
2024-04-20 19:05:03 +03:00
*Seriously, it's the `rm -rf /` of Cypher!*
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
## Other useful clauses
2017-04-13 18:21:23 +03:00
2024-04-20 19:05:03 +03:00
`PROFILE` - before a query, show its execution plan.
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
`COUNT(e)` - count entities (nodes or relationships) matching `e` .
2017-04-13 18:21:23 +03:00
2024-04-20 19:05:03 +03:00
`LIMIT x` - limit the result to the first `x` results.
2017-04-13 18:21:23 +03:00
2024-04-20 19:05:03 +03:00
## Special hints
2017-04-13 18:21:23 +03:00
2024-04-20 19:05:03 +03:00
- Cypher only has single-line comments, using double-slashes: `// comment`
- You can execute a Cypher script stored in a .cql file directly in Neo4j (it's an import). However, you can't have multiple statements in this file (separated by `;` ).
- Use the Neo4j shell to write Cypher, it's really awesome.
- Cypher will be the standard query language for all graph databases (known as [openCypher ](https://opencypher.org/ )).
2017-04-12 19:30:09 +03:00
2024-04-20 19:05:03 +03:00
Read more [here ](https://neo4j.com/developer/cypher-query-language/ ).
2017-04-12 19:30:09 +03:00