Dynamic labels/types

modules/ROOT/pages/clauses/create.adoc

@@ -205,6 +205,59 @@ Nodes created: 2 +
 Properties set: 4
 |===
 
+[role=label--new-5.26]
+[[dynamic-create]]
+== CREATE nodes and relationships using dynamic node labels and relationship types
+
+Node labels and relationship types can be referenced dynamically in expressions, parameters, and variables when creating nodes and relationships.
+
+.Syntax for creating nodes and relationships dynamically
+[source, syntax]
+----
+CREATE (n:$(<expr>)),
+CREATE ()-[r:$(<expr>)]->()
+----
+
+The expression must evaluate to a `STRING NOT NULL | LIST<STRING NOT NULL> NOT NULL` value.
+Using a `LIST<STRING>` with more than one item when creating a relationship using dynamic relationship types will fail.
+This is because a relationship can only have exactly one type.
+
+.Parameters
+[source, parameters]
+----
+{
+  "nodeLabels": ["Person", "Director"],
+  "relType": "DIRECTED",
+  "movies": ["Ladybird", "Little Women", "Barbie"]
+}
+----
+
+.Create nodes and relationships using dynamic node labels and relationship types
+[source, cypher]
+----
+CREATE (greta:$($nodeLabels) {name: 'Greta Gerwig'})
+WITH greta
+UNWIND $movies AS movieTitle
+CREATE (greta)-[:$($relType)]->(m:Movie {title: movieTitle})
+RETURN greta.name AS name, labels(greta) AS gretaLabels, collect(m.title) AS moviesDirected
+----
+
+.Result
+[role="queryresult",options="footer",cols="3*<m"]
+|===
+| name | gretaLabels | moviesDirected
+
+| "Greta Gerwig"
+| ["Person, "Director"]
+| ["Ladybird", "Little Women", "Barbie"]
+
+3+d|Rows: 1 +
+Nodes created: 4 +
+Relationships created: 3 +
+Properties set: 4 +
+Labels added: 5
+|===
+
 [role=label--new-5.18]
 [[insert-as-synonym-of-create]]
 == `INSERT` as a synonym of `CREATE`

modules/ROOT/pages/clauses/load-csv.adoc

@@ -299,6 +299,43 @@ Added 4 nodes, Set 8 properties, Added 4 labels
 |===
 ====
 
+[role=label--new-5.26]
+[[dynamic-columns]]
+=== Import CSV files using dynamic columns
+
+CSV columns can be referenced dynamically to map labels to nodes in the graph. This enables flexible data handling, allowing labels to be be populated from CSV column values without manually specifying each entry.
+
+.bands-with-headers.csv
+[source, csv, filename="artists-with-headers.csv"]
+----
+Id,Label,Name
+1,Band,The Beatles
+2,Band,The Rolling Stones
+3,Band,Pink Floyd
+4,Band,Led Zeppelin
+----
+
+.Query
+[source, cypher, role=test-skip]
+----
+LOAD CSV WITH HEADERS FROM 'file:///bands-with-headers.csv' AS line
+MERGE (n:$(line.Label) {name: line.Name})
+RETURN n AS bandNodes
+----
+
+.Result
+[role="queryresult",options="header,footer",cols="1*<m"]
+|===
+| bandNodes
+
+| (:Band {name: 'The Beatles'})
+| (:Band {name: 'The Rolling Stones'})
+| (:Band {name: 'Pink Floyd'})
+| (:Band {name: 'Led Zeppelin'})
+
+1+d|Rows: 4 +
+Added 4 nodes, Set 4 properties, Added 4 labels
+|===
 
 === Import compressed CSV files
 

modules/ROOT/pages/clauses/match.adoc

@@ -17,11 +17,11 @@ To recreate the graph, run the following query against an empty Neo4j database:
 
 [source, cypher, role=test-setup]
 ----
-CREATE (charlie:Person {name: 'Charlie Sheen'}),
-       (martin:Person {name: 'Martin Sheen'}),
-       (michael:Person {name: 'Michael Douglas'}),
-       (oliver:Person {name: 'Oliver Stone'}),
-       (rob:Person {name: 'Rob Reiner'}),
+CREATE (charlie:Person:Actor {name: 'Charlie Sheen'}),
+       (martin:Person:Actor {name: 'Martin Sheen'}),
+       (michael:Person:Actor {name: 'Michael Douglas'}),
+       (oliver:Person:Director {name: 'Oliver Stone'}),
+       (rob:Person:Director {name: 'Rob Reiner'}),
        (wallStreet:Movie {title: 'Wall Street'}),
        (charlie)-[:ACTED_IN {role: 'Bud Fox'}]->(wallStreet),
        (martin)-[:ACTED_IN {role: 'Carl Fox'}]->(wallStreet),
@@ -490,3 +490,122 @@ The above query uses the xref:functions/aggregating.adoc#functions-collect[`coll
 
 For more information about how Cypher queries work, see xref:clauses/clause-composition.adoc[].
 
+[role=label--new-5.26]
+[[dynamic-match]]
+== MATCH nodes and relationships using dynamic node labels and relationship types
+
+Node labels and relationship types can be referenced dynamically in expressions, parameters, and variables when matching nodes and relationships.
+
+.Syntax for matching node labels dynamically
+[source, syntax]
+----
+MATCH (n:$(<expr>))
+MATCH (n:$any(<expr>))
+MATCH (n:$all(<expr>))
+----
+
+[NOTE]
+`MATCH (n:$all(<expr>))` is functionally equivalent to `MATCH (n:$(<expr>))`.
+
+.Syntax for matching relationship types dynamically
+[source, syntax]
+----
+MATCH ()-[r:$(<expr>))]->()
+MATCH ()-[r:$any(<expr>)]->()
+MATCH ()-[r:$all(<expr>))]->()
+----
+
+The expression must evaluate to a `STRING NOT NULL | LIST<STRING NOT NULL> NOT NULL` value.
+If you use a `LIST<STRING>` with more than one item in a relationship pattern with dynamic relationship types, no results will be returned.
+This is because a relationship can only have exactly one type.
+
+.Match labels dynamically
+[source, cypher]
+----
+WITH ["Person", "Director"] AS labels
+MATCH (directors:$(labels))
+RETURN directors
+----
+
+.Result
+[role="queryresult",options="header,footer",cols="1*<m"]
+|===
+| directors
+
+| (:Person:Director {name: "Oliver Stone"})
+| (:Person:Director {name: "Rob Reiner"})
+
+1+d|Rows: 2
+|===
+
+.Match nodes dynamically using the `any()` function
+[source, cypher]
+----
+MATCH (n:$any(["Movie", "Actor"]))
+RETURN n AS nodes
+----
+
+[NOTE]
+The xref:functions/predicate.adoc#functions-any[`any()`] function matches nodes that have any of the specified labels.
+
+.Result
+[role="queryresult",options="header,footer",cols="1*<m"]
+|===
+| nodes
+
+| (:Person:Actor {name: "Charlie Sheen"})
+| (:Person:Actor {name: "Martin Sheen"})
+| (:Person:Actor {name: "Michael Douglas"})
+| (:Movie {title: "Wall Street"})
+| (:Movie {title: "The American President"})
+
+1+d|Rows: 5
+|===
+
+
+.Parameter
+[source, parameters]
+----
+{
+  "label": "Movie"
+}
+----
+
+.Match nodes dynamically using a parameter
+[source, cypher]
+----
+MATCH (movie:$($label))
+RETURN movie.title AS movieTitle
+----
+
+.Result
+[role="queryresult",options="header,footer",cols="1*<m"]
+|===
+| movieTitle
+
+| "Wall Street"
+| "The American President"
+
+1+d|Rows: 2
+|===
+
+
+.Match relationships dynamically using a variable
+[source, cypher]
+----
+CALL db.relationshipTypes()
+YIELD relationshipType
+MATCH ()-[r:$(relationshipType)]->()
+RETURN relationshipType, count(r) AS relationshipCount
+----
+
+.Result
+[role="queryresult",options="header,footer",cols="2*<m"]
+|===
+| relationshipType | relationshipCount
+
+| "ACTED_IN" | 5
+| "DIRECTED" | 2
+
+2+d|Rows: 2
+|===

modules/ROOT/pages/clauses/merge.adoc

@@ -683,3 +683,57 @@ RETURN person.name, person.bornIn, person.chauffeurName
 | person.name | person.bornIn | person.chauffeurName
 | "Keanu Reeves" | "Beirut" | "Eric Brown"
 |===
+
+[role=label--new-5.26]
+[[dynamic-merge]]
+== MERGE nodes and relationships using dynamic node labels and relationship types
+
+Node labels and relationship types can be referenced dynamically in expressions, parameters, and variables when merging nodes and relationships.
+
+.Syntax for merging nodes and relationships dynamically
+[source, syntax]
+----
+MERGE (n:$(<expr>)),
+MERGE ()-[r:$(<expr>)]->()
+----
+
+The expression must evaluate to a `STRING NOT NULL | LIST<STRING NOT NULL> NOT NULL` value.
+Using a `LIST<STRING>` with more than one item when merging a relationship using dynamic relationship types will fail.
+This is because a relationship can only have exactly one type.
+
+.Parameters
+[source, parameters]
+----
+{
+  "nodeLabels": ["Person", "Director"],
+  "relType": "DIRECTED",
+  "movies": ["Ladybird", "Little Women", "Barbie"]
+}
+----
+
+.Merge nodes and relationships using dynamic node labels and relationship types
+[source, cypher]
+----
+MERGE (greta:$($nodeLabels) {name: 'Greta Gerwig'})
+WITH greta
+UNWIND $movies AS movieTitle
+MERGE (greta)-[:$($relType)]->(m:Movie {title: movieTitle})
+RETURN greta.name AS name, labels(greta) AS gretaLabels, collect(m.title) AS moviesDirected
+----
+
+.Result
+[role="queryresult",options="footer",cols="3*<m"]
+|===
+| name | gretaLabels | moviesDirected
+
+| "Greta Gerwig"
+| ["Person, "Director"]
+| ["Ladybird", "Little Women", "Barbie"]
+
+3+d|Rows: 1 +
+Nodes created: 4 +
+Relationships created: 3 +
+Properties set: 4 +
+Labels added: 5
+|===
+

modules/ROOT/pages/clauses/remove.adoc

@@ -69,8 +69,8 @@ Properties set: 1
 Instead, using xref::clauses/set.adoc#set-remove-properties-using-empty-map[`SET` with `=` and an empty map as the right operand] will clear all properties from the node or relationship.
 
 [role=label--new-5.24]
-[[remove-remove-a-property-dynamically]]
-== Dynamically removing a property
+[[dynamic-remove-property]]
+== Dynamically remove a property
 
 `REMOVE` can be used to remove a property on a node or relationship even when the property key name is not statically known.
 
@@ -82,7 +82,6 @@ REMOVE n[key]
 The dynamically calculated key must evaluate to a `STRING` value.
 This query creates a copy of every property on the nodes:
 
-
 .Query
 [source, cypher, indent=0]
 ----
@@ -131,18 +130,19 @@ Labels removed: 1
 |===
 
 [role=label--new-5.24]
-[[remove-remove-a-label-dynamically-from-a-node]]
-== Dynamically removing a label
+[[dynamic-remove-node-label]]
+== Dynamically remove a node label
 
 `REMOVE` can be used to remove a label on a node even when the label is not statically known.
 
-
 [source, syntax]
 ----
 MATCH (n)
 REMOVE n:$(expr)
 ----
 
+The expression must evaluate to a `STRING NOT NULL | LIST<STRING NOT NULL> NOT NULL` value.
+
 .Query
 [source, cypher, indent=0]
 ----

modules/ROOT/pages/clauses/set.adoc

@@ -162,8 +162,8 @@ Properties set: 1
 
 
 [role=label--new-5.24]
-[[set-dynamically-a-property]]
-== Dynamically setting or updating a property
+[[dynamic-set-property]]
+== Dynamically set or update a property
 
 `SET` can be used to set or update a property on a node or relationship even when the property key name is not statically known.
 
@@ -541,8 +541,8 @@ Labels added: 1
 |===
 
 [role=label--new-5.24]
-[[set-set-a-dynamic-label-on-a-node]]
-== Dynamically setting a label
+[[dynamic-set-node-label]]
+== Dynamically set a node label
 
 `SET` can be used to set a label on a node even when the label is not statically known.