-
Notifications
You must be signed in to change notification settings - Fork 62
Document VECTOR
type and new vector functions
#1299
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.
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
base: cypher-25
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, great! :D
modules/ROOT/pages/expressions/predicates/type-predicate-expressions.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Outdated
Show resolved
Hide resolved
modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
Show resolved
Hide resolved
@@ -26,7 +27,7 @@ In this example `VECTOR` type value, `[1.05, 0.123, 5]` is the coordinates of th | |||
[NOTE] | |||
The dimensions and the formatting of a `VECTOR` is similar to a xref:values-and-types/lists.adoc[`LIST`] value. | |||
However, unlike `LIST` values which contain elements that can be accessed individually with xref:expressions/list-expressions.adoc[list expressions], all operations on a `VECTOR` must operate on the entire `VECTOR`; it is not possible to access or slice individual dimensions of a `VECTOR` value. | |||
Additionally, a `LIST` cannot contain `VECTOR` values. | |||
Additionally, a `LIST` cannot store `VECTOR` values. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Neo4j cannot store Lists containing vector values, slight difference
|
||
| If a `STRING` is used in `vectorValue`, it must start and end with square brackets (`[]`). | ||
The values inside the brackets must be a number represented in either decimal or scientific notation and must be comma separated. | ||
| `null`, `NaN`, and `Infinity` values are not allowed as elements in the `LIST` used as `vectorValue`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe:
| `null`, `NaN`, and `Infinity` values are not allowed as elements in the `LIST` used as `vectorValue`. | |
| `null`, `NaN`, and `Infinity` values are not allowed as coordinate values. |
This PR includes documentation updates New pages: Updated pages: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
[[vector-type]] | ||
== The vector type | ||
|
||
The `VECTOR` type is a fixed-length, ordered collection of of numeric coordinate values (`INTEGER` or `FLOAT`) stored as a single unit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The `VECTOR` type is a fixed-length, ordered collection of of numeric coordinate values (`INTEGER` or `FLOAT`) stored as a single unit. | |
The `VECTOR` type is a fixed-length, ordered collection of numeric coordinate values (`INTEGER` or `FLOAT`) stored as a single unit. |
TO-DO:
NOT in this PR: