Skip to content

docs: support RANGE keyword in CREATE INDEX ... FOR syntax - #1702

Merged
vpavicic merged 2 commits into
release/3.13from
feat/create-range-index-syntax
Jul 28, 2026
Merged

docs: support RANGE keyword in CREATE INDEX ... FOR syntax#1702
vpavicic merged 2 commits into
release/3.13from
feat/create-range-index-syntax

Conversation

@imilinovic

Copy link
Copy Markdown
Contributor

Release note

Documented support for the RANGE keyword in the CREATE INDEX ... FOR syntax, so Neo4j DDL such as CREATE RANGE INDEX FOR (n:Person) ON (n.id) runs unchanged in Memgraph — RANGE is 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:

  • Add appropriate milestone (current release cycle)
  • Add bugfix or feature label, based on the product PR type you're documenting
  • Make sure all relevant tech details are documented
  • Check all content with Grammarly
  • Perform a self-review of my code
  • The build passes locally
  • My changes generate no new warnings or errors

@imilinovic imilinovic added this to the 3.13 milestone Jul 27, 2026
@imilinovic imilinovic added the feature Documentation related to a new product feature of feature update label Jul 27, 2026
@imilinovic imilinovic self-assigned this Jul 27, 2026
@vercel

vercel Bot commented Jul 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
documentation Ready Ready Preview, Comment Jul 27, 2026 12:47pm

Request Review

@imilinovic
imilinovic marked this pull request as ready for review July 27, 2026 12:43
@vpavicic vpavicic mentioned this pull request Jul 28, 2026
33 tasks
@vpavicic
vpavicic merged commit c87ada7 into release/3.13 Jul 28, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature Documentation related to a new product feature of feature update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants