docs: support RANGE keyword in CREATE INDEX ... FOR syntax - #1702
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
imilinovic
marked this pull request as ready for review
July 27, 2026 12:43
imilinovic
requested review from
Josipmrden,
gitbuda and
vpavicic
as code owners
July 27, 2026 12:43
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release note
Documented support for the
RANGEkeyword in theCREATE INDEX ... FORsyntax, so Neo4j DDL such asCREATE RANGE INDEX FOR (n:Person) ON (n.id)runs unchanged in Memgraph —RANGEis accepted as a synonym for the existing label-property / edge-type property index.Related product PRs
PRs from product repo this doc page is related to:
memgraph/memgraph#4486
Checklist:
bugfixorfeaturelabel, based on the product PR type you're documenting