From cbd013ee6243204e1be24f1609ae92d833c74513 Mon Sep 17 00:00:00 2001 From: lidiazuin Date: Thu, 5 Jun 2025 10:47:32 +0200 Subject: [PATCH] Fixing problem with label --- modules/ROOT/pages/planning-and-tuning/runtimes/concepts.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/ROOT/pages/planning-and-tuning/runtimes/concepts.adoc b/modules/ROOT/pages/planning-and-tuning/runtimes/concepts.adoc index 7f31be37d..56602fd49 100644 --- a/modules/ROOT/pages/planning-and-tuning/runtimes/concepts.adoc +++ b/modules/ROOT/pages/planning-and-tuning/runtimes/concepts.adoc @@ -234,7 +234,7 @@ Unlike interpreted runtimes, compiled runtimes have a code generation phase foll As stated xref::planning-and-tuning/runtimes/concepts.adoc#runtimes-slotted-runtime-considerations[above], there are rare scenarios in which users of Neo4j Enterprise Edition may benefit from not using the pipelined runtime for their queries. However, for most queries, the pipelined runtime is a more efficient runtime capable of handling all operators and queries. -[role=label--enterprise-edition label] +[role=label--enterprise-edition] [[runtimes-parallel-runtime]] == Parallel runtime