Skip to content

Fix version exact roles #1095

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 31, 2024
Merged

Fix version exact roles #1095

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a30da8a
fix
JPryce-Aklundh Oct 31, 2024
61663a3
fix
JPryce-Aklundh Oct 31, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions modules/ROOT/pages/appendix/tutorials/advanced-query-tuning.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Let's explain how to use these features with a more advanced query tuning exampl

[NOTE]
====
If you are upgrading an existing store to {neo4j-version-exact}, it may be necessary to drop and re-create existing indexes.
If you are upgrading an existing store, it may be necessary to drop and re-create existing indexes.
For information on native index support and upgrade considerations regarding indexes, see link:{neo4j-docs-base-uri}/operations-manual/{page-version}/performance/index-configuration[Operations Manual -> Performance -> Index configuration].
====

Expand Down Expand Up @@ -936,10 +936,10 @@ Predicates that will not work:

[NOTE]
====
If there is an existence constraint on the property, no predicate is required to trigger the optimization.
If there is a xref:constraints/managing-constraints.adoc#create-property-existence-constraints[property existence constraint] on the property, no predicate is required to trigger the optimization.
For example, `CREATE CONSTRAINT constraint_name FOR (p:Person) REQUIRE p.name IS NOT NULL`

As of Neo4j {neo4j-version-exact}, predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
Predicates with parameters, such as `WHERE n.prop > $param`, can trigger _index-backed ORDER BY_.
The only exception are queries with parameters of type `POINT`.
====

Loading