Skip to content

Commit f5d97d2

Browse files
2025.02 to 2025.03
1 parent 7366a5a commit f5d97d2

File tree

8 files changed

+8
-8
lines changed

8 files changed

+8
-8
lines changed

modules/ROOT/pages/queries/composed-queries/combined-queries.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -157,7 +157,7 @@ ORDER BY count
157157

158158
For more information, see xref:subqueries/call-subquery.adoc#call-post-union[`CALL` subqueries -> Post-union processing].
159159

160-
[role=label--new-2025.02]
160+
[role=label--new-2025.03]
161161
[[combining-union-and-union-all]]
162162
== Combining UNION and UNION ALL
163163

modules/ROOT/pages/queries/composed-queries/conditional-queries.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
= Conditional queries (`WHEN`)
22
:description: Information about how to use `WHEN` to construct conditional queries in Cypher.
3-
:page-role: new-2025.02
3+
:page-role: new-2025.03
44

55
`WHEN`, together with `THEN` and `ELSE`, enables different branches of a query to execute based on certain conditions.
66
In this way, it performs similar a control-flow mechanism to the `IF` statement in other programming languages.

modules/ROOT/pages/queries/composed-queries/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,4 +8,4 @@ As such, `UNION` and `WHEN` manage in different ways the execution flow and logi
88
For more information, see:
99

1010
* xref:queries/composed-queries/combined-queries.adoc[]
11-
* xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.02]
11+
* xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.03]

modules/ROOT/pages/queries/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,5 +8,5 @@ It also discusses how to compose combined queries using `UNION` and conditional
88
* xref:queries/basic.adoc[]
99
* xref:queries/composed-queries/index.adoc[]
1010
** xref:queries/composed-queries/combined-queries.adoc[]
11-
** xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.02]
11+
** xref:queries/composed-queries/conditional-queries.adoc[] label:new[Introduced in Neo4j 2025.03]
1212

modules/ROOT/pages/subqueries/call-subquery.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -484,7 +484,7 @@ Now all `Player` nodes, regardless of whether they have any `PLAYS_FOR` relation
484484
485485
====
486486

487-
[role=label--new-2025.02]
487+
[role=label--new-2025.03]
488488
[[conditional-call]]
489489
== Conditional `CALL` subqueries
490490

modules/ROOT/pages/subqueries/collect.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ RETURN person.name as name, COLLECT {
7474
2+d|Rows: 3
7575
|===
7676

77-
[role=label--new-2025.02]
77+
[role=label--new-2025.03]
7878
[[conditional-collect]]
7979
== Conditional `COLLECT` subquery
8080

modules/ROOT/pages/subqueries/count.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ RETURN person.name AS name
7171
1+d|Rows: 1
7272
|===
7373

74-
[role=label--new-2025.02]
74+
[role=label--new-2025.03]
7575
[[conditional-count]]
7676
== Conditional `COUNT` subquery
7777

modules/ROOT/pages/subqueries/existential.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ RETURN person.name AS name
7373
1+d|Rows: 1
7474
|===
7575

76-
[role=label--new-2025.02]
76+
[role=label--new-2025.03]
7777
[[conditional-exists]]
7878
== Conditional `EXISTS` subqueries
7979

0 commit comments

Comments
 (0)