VECTOR property type constraints #1325
Merged
+160
−87
Conversation
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
Hunterness
reviewed
Jul 2, 2025
Hunterness
reviewed
Sep 16, 2025
Draft
Hunterness
reviewed
Oct 8, 2025
modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
Outdated
Show resolved
Hide resolved
| .Create `VECTOR` property type constraints label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.10] | ||
| ====== | ||
| It is necessary to specify both the dimension and the coordinate type of any constrained `VECTOR` properties. |
There was a problem hiding this comment.
Suggested change
| It is necessary to specify both the dimension and the coordinate type of any constrained `VECTOR` properties. | |
| It is necessary to specify both the dimension and the coordinate type of all constrained `VECTOR` properties. |
or
Suggested change
| It is necessary to specify both the dimension and the coordinate type of any constrained `VECTOR` properties. | |
| It is necessary to specify both the dimension and the coordinate type of any constrained `VECTOR` property. |
maybe? sounded odd to me with any ... properties
| * `ZONED DATETIME` | ||
| * `DURATION` | ||
| * `POINT` | ||
| * `VECTOR<TYPE>(DIMENSION)` label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.10] |
There was a problem hiding this comment.
should we say what TYPE and DIMENSION is here? it's mentioned on the syntax page in the note below, and exists up by the example of vector property type constraints but not in this list of allowed types
stefano-ottolenghi
added a commit
that referenced
this pull request
Oct 9, 2025
See also: #1325 Co-authored-by: Stefano Ottolenghi <[email protected]>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
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.
This PR will fail for now because it uses xrefs pointing to unmerged changes (part of #1299)
See also:
#1299
TODO:
Confirm release version (and update all instances of "2025.xx" in this PR to whatever that version is)IMPORTANT: The changes made to managing-constraints.adoc must be ported over to constraints/create-constraints.adoc, constraints/list-constraints.adoc and schema/syntax.adoc (in #1395) once this PR has been merged (assuming vector type constraints go live before graph types)