Update descriptions in show index columns #1403
Merged
+5
−3
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
was missing vector type and the entity type values was odd (now they're aligned with the constraints one and more accurate to what values it actually returns)
mnd999
approved these changes
Oct 14, 2025
also on the allowed types section on the main constraint page and not just the syntax page (it was mentioned in the example but not by the type list) unrelated to the index bits, but something I noticed on the constraint PR but that didn't get updated before it was merged
rsill-neo4j
approved these changes
Oct 15, 2025
|
|
||
| [NOTE] | ||
| Because storing lists of xref:values-and-types/vector.adoc[`VECTOR`] values is not supported, property type constraints cannot be created for `LIST<VECTOR<TYPE>(DIMENSION) NOT NULL>`. | ||
| Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less or equal to `4096`. |
There was a problem hiding this comment.
Suggested change
| Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less or equal to `4096`. | |
| Additionally, `VECTOR` property type constraints must be created with a specific dimension and coordinate value, where the dimension must be greater than `0` and less than or equal to `4096`. |
There was a problem hiding this comment.
I copied this directly from the syntax page, do you want me to update it there too?
There was a problem hiding this comment.
updated in both
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
|
also applied this to #1406 (graph types) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
was missing vector type in the index type column and the entity type values were odd (now they're aligned with the constraints one and more accurate to what values it actually returns)
the vector in the index type column should have been added when vector indexes were introduced, the entity type column update is just general from the beginning of show indexes.
the vector property type constraint update is only relevant for cypher 25 after the vector type was released