Not a path pattern expression

modules/ROOT/content-nav.adoc

@@ -76,6 +76,7 @@
 *** xref:expressions/predicates/comparison-operators.adoc[]
 *** xref:expressions/predicates/list-operators.adoc[]
 *** xref:expressions/predicates/string-operators.adoc[]
+*** xref:expressions/predicates/label-expression-predicates.adoc[]
 *** xref:expressions/predicates/path-pattern-expressions.adoc[]
 *** xref:expressions/predicates/type-predicate-expressions.adoc[]
 ** xref:expressions/node-relationship-operators.adoc[]

modules/ROOT/pages/expressions/index.adoc

@@ -10,6 +10,7 @@ For details and examples of specific expressions, see the following sections:
 ** xref:expressions/predicates/comparison-operators.adoc[]: `=`, `<>`, `<`, `>`, `\<=`, `>=`, `IS NULL`, `IS NOT NULL`
 ** xref:expressions/predicates/list-operators.adoc[]: `IN`
 ** xref:expressions/predicates/string-operators.adoc[]: `STARTS WITH`, `ENDS WITH`, `CONTAINS`, `IS NORMALIZED`, `IS NOT NORMALIZED`, `=~`
+** xref:expressions/predicates/label-expression-predicates.adoc[]: information about how to test whether a node or relationship matches a label expression or not.
 ** xref:expressions/predicates/path-pattern-expressions.adoc[]: information about filtering queries with path pattern expressions.
 ** xref:expressions/predicates/type-predicate-expressions.adoc[]: information about how to verify the value type of a Cypher expression.
 * xref:expressions/node-relationship-operators.adoc[]: information about how to access `NODE` and `RELATIONSHIP` property values with `.` and `[]`.

modules/ROOT/pages/expressions/predicates/index.adoc

@@ -9,6 +9,7 @@ This chapter is divided into the following sections:
 * xref:expressions/predicates/comparison-operators.adoc[]: `=`, `<>`, `<`, `>`, `\<=`, `>=`, `IS NULL`, `IS NOT NULL`
 * xref:expressions/predicates/list-operators.adoc[]: `IN`
 * xref:expressions/predicates/string-operators.adoc[]: `STARTS WITH`, `ENDS WITH`, `CONTAINS`, `IS NORMALIZED`, `IS NOT NORMALIZED`, `=~`
+* xref:expressions/predicates/label-expression-predicates.adoc[]: information about how to test whether a node or relationship matches a label expression or not.
 * xref:expressions/predicates/path-pattern-expressions.adoc[]: information about filtering queries with path pattern expressions.
 * xref:expressions/predicates/type-predicate-expressions.adoc[]: information about how to verify the value type of a Cypher expression.
 

modules/ROOT/pages/expressions/predicates/label-expression-predicates.adoc

@@ -0,0 +1,243 @@
+= Label expression predicates
+:description: This page describes how to use label expression predicates with Cypher.
+
+You can use a label expression predicate to verify that the labels of a node or the relationship type of a relationship match a given label expression.
+
+[[label-expression-predicat-syntax]]
+== Syntax
+
+[source, syntax]
+----
+<expr>:<label-expression>
+----
+
+Where `<expr>` is any Cypher expression and `<label-expression>` is any Cypher xref::patterns/reference.adoc#label-expressions[label expression].
+
+[[example-graph]]
+== Example graph
+
+The following graph is used for the examples on this page:
+
+image::label_expression_predicates_graph.svg[width="700",role="middle"]
+
+To recreate the graph, run the following query against an empty Neo4j database:
+
+[source, cypher]
+----
+CREATE (alice:Person&Manager {name:'Alice', age: 65, skills: ['Java', 'Python']}),
+       (cecil:Person&Developer {name: 'Cecil', age: 25, skills: ['Java', 'Python']}),
+       (cecilia:Person&Developer {name: 'Cecilia', age: 31, skills: ['JavaScript', 'TypeScript']}),
+       (charlie:Person&Engineer {name: 'Charlie', age: 61, skills: ['C++', 'Python']}),
+       (daniel:Person&Director {name: 'Daniel', age: 39, skills: ['JavaScript', 'Slides']}),
+       (eskil:Person&CEO {name: 'Eskil', age: 39, skills: ['Slides', 'ChatGPT']}),
+
+       (cecil)-[:WORKS_FOR]->(alice),
+       (cecilia)-[:WORKS_FOR]->(alice),
+       (charlie)-[:WORKS_FOR]->(daniel),
+       (alice)-[:REPORTS_TO]->(daniel),
+       (daniel)-[:REPORTS_TO]->(eskil)
+----
+
+[node-label-expression-predicate]
+== Test whether a node has a certain label
+
+Given that `p` is a node, `p:Manager` tests whether `p` has the label `Manager` or not and results in `true` or `false`, respectively.
+
+[source, cypher]
+----
+MATCH (p:Person)
+RETURN p.name AS name, p:Manager AS isManager
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | isManager
+
+| "Alice" | true
+| "Cecil" | false
+| "Cecilia" | false
+| "Charlie" | false
+| "Daniel" | false
+| "Eskil" | false
+
+2+d|Rows: 6
+|===
+
+Given that `p` is a node and a more complex xref::patterns/reference.adoc#label-expressions[label expression], e.g, `Manager|Director|CEO`, `p:Manager|Director|CEO` tests whether node `p` matches the label expression `Manager|Director|CEO` or not and results in `true` or `false`, respectively.
+More specifically, `p:Manager|Director|CEO` tests whether `p` has at least one of the three labels `Manager`, `Director`, and `CEO`.
+
+[source, cypher]
+----
+MATCH (p:Person)
+RETURN p.name AS name,
+       p:Manager|Director|CEO AS isManager
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | isManager
+
+| "Alice" | true
+| "Cecil" | false
+| "Cecilia" | false
+| "Charlie" | false
+| "Daniel" | true
+| "Eskil" | true
+
+2+d|Rows: 6
+|===
+
+`p:!CEO` tests whether `p` does not have the label `CEO`.
+
+[source, cypher]
+----
+MATCH (p:Person)-[r]->(m)
+RETURN p.name AS name,
+       m:!CEO AS doesNotWorkDirectlyForTheCEO
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | doesNotWorkDirectlyForTheCEO
+
+| "Alice" | true
+| "Cecil" | true
+| "Cecilia" | true
+| "Charlie" | true
+| "Daniel" | false
+
+2+d|Rows: 5
+|===
+
+When `<exp>` results in ´null`, then the label expression predicate results in `null`, e.g. if `p` is `null`, then `p:!CEO` results in `null`.
+
+[source, cypher]
+----
+MATCH (p:Person)
+OPTIONAL MATCH (p)-[r]->(m)
+RETURN p.name AS name,
+       m:!CEO AS doesNotWorkDirectlyForTheCEO
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | doesNotWorkDirectlyForTheCEO
+
+| "Alice" | true
+| "Cecil" | true
+| "Cecilia" | true
+| "Charlie" | true
+| "Daniel" | false
+| "Eskil" | null
+
+2+d|Rows: 6
+|===
+
+The function xref:functions/scalar.adoc#functions-coalesce[coalesce] allows to turn `null` into a default value:
+
+[source, cypher]
+----
+MATCH (p:Person)
+OPTIONAL MATCH (p)-[r]->(m)
+RETURN p.name AS name,
+       coalesce(m:!CEO, false) AS doesNotWorkDirectlyForTheCEO
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | doesNotWorkDirectlyForTheCEO
+
+| "Alice" | true
+| "Cecil" | true
+| "Cecilia" | true
+| "Charlie" | true
+| "Daniel" | false
+| "Eskil" | false
+
+2+d|Rows: 6
+|===
+
+[role=label--new-Neo4j-2025.07 label--cypher-25-only]
+[[dynamic-node-label-expression-predicate]]
+== Test whether a node matches a dynamic label expression
+
+If you don't know the manager labels, you can infer a list of `managerLabels` by collecting all non-`Person` labels from people with a direct report.
+You can test nodes with the label expression predicate to match a xref:patterns/reference.adoc#dynamic-label-and-type-expressions[dynamic label expression].
+`p:$any(managerLabels)` tests whether a node `p` has at least on of the label in the list `managerLabels`.
+
+[source, cypher]
+----
+MATCH ()-[r]->(p:Person)
+UNWIND labels(p) AS label
+FILTER label <> "Person"
+RETURN COLLECT(label) AS managerLabels
+NEXT
+MATCH (p)
+RETURN p.name AS name, p:$any(managerLabels) AS isManager
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | isManager
+
+| "Alice" | true
+| "Cecil" | false
+| "Cecilia" | false
+| "Charlie" | false
+| "Daniel" | true
+| "Eskil" | true
+
+2+d|Rows: 6
+|===
+
+[node-label-expression-predicate]
+== Test whether a relationship has a certain relationship type
+
+Given that `r` is a relationship, `r:WORKS_FOR` tests whether `r` has the relationship type `WORKS_FOR` or not and result in `true` or `false`, respectively.
+
+[source, cypher]
+----
+MATCH (p:Person)-[r]->()
+RETURN p.name AS name,
+       r:WORKS_FOR AS isNotManager
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | isNotManager
+
+| "Alice" | false
+| "Cecil" | true
+| "Cecilia" | true
+| "Charlie" | true
+| "Daniel" | false
+
+2+d|Rows: 5
+|===
+
+If `r` is `null`, then the label expression predicate, e.g. `r:WORKS_FOR|REPORTS_TO`, results in `null`.
+The function xref:functions/scalar.adoc#functions-coalesce[coalesce] allows to turn `null` into a default value.
+
+[source, cypher]
+----
+MATCH (p:Person)
+OPTIONAL MATCH ()-[r]->(p)
+RETURN DISTINCT
+  p.name AS name,
+  coalesce(r:WORKS_FOR|REPORTS_TO, false) AS hasReports
+----
+
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| name | hasReports
+
+| "Alice" | true
+| "Cecil" | false
+| "Cecilia" | false
+| "Charlie" | false
+| "Daniel" | true
+| "Eskil" | true
+
+2+d|Rows: 6
+|===
+

modules/ROOT/pages/expressions/predicates/path-pattern-expressions.adoc

@@ -127,3 +127,59 @@ RETURN exists((:Person)-[:WORKS_FOR {since: 2023}]->(:Person {name: "Alice"})) A
 
 1+d|Rows: 1
 |===
+
+[[not-patterns]]
+== Expressions similar to path pattern expressions
+
+Since any expression can be wrapped in parentheses, some are very similar to path pattern expressions.
+For example:
+
+`(p:Person)` is not a path pattern expression since it does not have at least one xref::patterns/reference.adoc#relationship-patterns[relationship] or xref::patterns/reference.adoc#variable-length-relationships[variable-length relationship].
+Instead, `(p:Person)` is the xref:expressions/predicates/label-expression-predicates.adoc[label expression predicate] `p:Person` in parentheses.
+
+.Parenthesized label expression predicate
+[source, cypher]
+----
+MATCH (employee:Person)-[:WORKS_FOR]->(p)
+  WHERE (p:Person)
+RETURN employee.name AS employee, (p:Person) AS workForAPeron
+----
+
+The query result however is the same for both `p:Person` and `(p:Person)`:
+[source, cypher]
+----
+MATCH (employee:Person)-[:WORKS_FOR]->(p)
+  WHERE p:Person
+RETURN employee.name AS employee, p:Person AS workForAPerson
+----
+
+.Result
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| employee | workForAPerson
+
+| "Cecil" | true
+| "Cecilia" | true
+
+2+d|Rows: 2
+|===
+
+`(p)` is not a path pattern expression since it does not have at least one xref::patterns/reference.adoc#relationship-patterns[relationship] or xref::patterns/reference.adoc#variable-length-relationships[variable-length relationship].
+Instead, `(p)` is the variable `p` in parentheses.
+
+`(p)` does result in the value of variable `p`.
+If `p` is not a Boolean, then `(p)` does not result in a Boolean either.
+Hence, the following query throws an error:
+
+.Parenthesized node variable
+[source, cypher, role=test-fail]
+----
+MATCH (employee:Person)-[:WORKS_FOR]->(p)
+  WHERE (p)
+RETURN employee.name AS employee
+----
+
+[source, error]
+----
+Invalid input 'Node' for `p`. Expected to be Boolean.
+----