@@ -154,7 +154,7 @@ This is particularly useful when aggregating values.
154154In the following example, `NEXT` passes the variable `customer` to the second query:
155155
156156.Aggregation after `NEXT`
157- tag::sequential_queries_aggregation_example []
157+ // tag::sequential_queries_aggregation []
158158[source,cypher]
159159----
160160MATCH (c:Customer)-[:BUYS]->(p:Product)
165165RETURN product.name AS product,
166166 COUNT(customer) AS numberOfCustomers
167167----
168- end::sequential_queries_aggregation_example []
168+ // end::sequential_queries_aggregation []
169169
170170.Result
171171[role="queryresult",options="header,footer",cols="2*<m"]
@@ -190,7 +190,7 @@ end::sequential_queries_aggregation_example[]
190190If a `UNION` query follows a `NEXT` the full table of intermediate results is passed into all arms of the `UNION` query.
191191
192192.`UNION` after `NEXT`
193- tag::sequential_queries_union_example []
193+ // tag::sequential_queries_union []
194194[source,cypher]
195195----
196196MATCH (c:Customer)-[:BUYS]->(p:Product)
206206
207207RETURN * ORDER BY name, type
208208----
209- end::sequential_queries_union_example []
209+ // end::sequential_queries_union []
210210
211211.Result
212212[role="queryresult",options="header,footer",cols="3*<m"]
@@ -383,6 +383,7 @@ Conditional queries act similar to `CALL` by processing the incoming table of in
383383A conditional query following a `NEXT` acts equivalent to a conditional query wrapped in a `CALL` subquery.
384384
385385.Conditional query inside `NEXT`
386+ // tag::sequential_queries_chaining_conditional_queries[]
386387[source,cypher]
387388----
388389MATCH (c:Customer)-[:BUYS]->(:Product)<-[:SUPPLIES]-(s:Supplier)
@@ -406,6 +407,7 @@ WHEN size(personalities) > 1 THEN
406407ELSE
407408 RETURN customer, personalities[0] AS personality
408409----
410+ // end::sequential_queries_chaining_conditional_queries[]
409411
410412.Result
411413[role="queryresult",options="header,footer",cols="2*<m"]
0 commit comments