Skip to content
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.

Sign up for GitHub

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

Small fixes #749

Merged
merged 1 commit into from
Sep 27, 2023
+9 −9
Merged

Small fixes #749

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions modules/ROOT/pages/functions/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -155,7 +155,7 @@ These functions return a single value.
| Converts a value to a `BOOLEAN` value, or null if the value cannot be converted.

1.2+| xref::functions/scalar.adoc#functions-tofloat[`toFloat()`]
| `toFloat(input :: INTEGER | FLOAT) :: FLOAT`
| `toFloat(input :: INTEGER \| FLOAT) :: FLOAT`
| Converts an `INTEGER` value to a `FLOAT` value.
| `toFloat(input :: STRING) :: FLOAT`
| Converts a `STRING` value to a `FLOAT` value.
Expand All @@ -165,7 +165,7 @@ These functions return a single value.
| Converts a value to a `FLOAT` value, or null if the value cannot be converted.

1.3+| xref::functions/scalar.adoc#functions-tointeger[`toInteger()`]
| `toInteger(input :: INTEGER | FLOAT) :: INTEGER`
| `toInteger(input :: INTEGER \| FLOAT) :: INTEGER`
| Converts a `FLOAT` value to an `INTEGER` value.
| `toInteger(input :: BOOLEAN) :: INTEGER`
| Converts a `BOOLEAN` value to an `INTEGER` value.
Expand Down Expand Up @@ -361,9 +361,9 @@ These functions all operate on numerical expressions only, and will return an er
1.3+| xref::functions/mathematical-numeric.adoc#functions-round[`round()`]
| `round(input :: FLOAT) :: FLOAT`
| Returns the value of a number rounded to the nearest `INTEGER`.
| `round(value :: FLOAT, precision :: INTEGER | FLOAT) :: FLOAT`
| `round(value :: FLOAT, precision :: INTEGER \| FLOAT) :: FLOAT`
| Returns the value of a number rounded to the specified precision using rounding mode HALF_UP.
| `round(value :: FLOAT, precision :: INTEGER | FLOAT, mode :: STRING) :: FLOAT`
| `round(value :: FLOAT, precision :: INTEGER \| FLOAT, mode :: STRING) :: FLOAT`
| Returns the value of a number rounded to the specified precision with the specified rounding mode.

1.2+| xref::functions/mathematical-numeric.adoc#functions-sign[`sign()`]
Expand Down Expand Up @@ -571,11 +571,11 @@ Values of the xref::values-and-types/temporal.adoc[temporal types] -- `DATE`, `Z
| Creates a `ZONED DATETIME` instant.

1.1+| xref::functions/temporal/index.adoc#functions-datetime-timestamp[`datetime.fromepoch()`]
| `datetime.fromepoch(seconds :: INTEGER | FLOAT, nanoseconds :: INTEGER | FLOAT) :: ZONED DATETIME`
| `datetime.fromepoch(seconds :: INTEGER \| FLOAT, nanoseconds :: INTEGER \| FLOAT) :: ZONED DATETIME`
| Creates a `ZONED DATETIME` given the seconds and nanoseconds since the start of the epoch.

1.1+| xref::functions/temporal/index.adoc#functions-datetime-timestamp[`datetime.fromepochmillis()`]
| `datetime.fromepochmillis(milliseconds :: INTEGER | FLOAT) :: ZONED DATETIME`
| `datetime.fromepochmillis(milliseconds :: INTEGER \| FLOAT) :: ZONED DATETIME`
| Creates a `ZONED DATETIME` given the milliseconds since the start of the epoch.

1.1+| xref::functions/temporal/index.adoc#functions-datetime-realtime[`datetime.realtime()`]
Expand Down
2 changes: 1 addition & 1 deletion modules/ROOT/pages/functions/scalar.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1499,7 +1499,7 @@ With this in mind, the below list contains all supported types (as of Neo4j 5.13

This should be taken into account when relying on the output of the `valueType()` function.

See the xref::syntax/expressions.adoc#type-predicate-expressions[type predicate expression] for an alternative way of testing type values.
See the xref::values-and-types/type-predicate.adoc[type predicate expression] for an alternative way of testing type values.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be plural as well, right? ("type predicate expressions")

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well it is just one expression though 🤔 Would we say "see the Count Expression" or "see the Count Expressions"? :)



.+valueType()+
Expand Down
4 changes: 2 additions & 2 deletions modules/ROOT/pages/values-and-types/property-structural-constructed.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ For more details, see xref::values-and-types/working-with-null.adoc[working with

The table below shows the types and their syntactic synonyms.

These types (and their synonyms) can be used in xref::syntax/expressions.adoc#type-predicate-expressions[type predicate expressions] and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
These types (and their synonyms) can be used in xref::values-and-types/type-predicate.adoc[type predicate expressions] and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
They are also returned as a `STRING` value when using the xref::functions/scalar.adoc#functions-valueType[valueType()] function.

However, not all types can be used in all places.
Expand Down Expand Up @@ -119,7 +119,7 @@ The type `PROPERTY VALUE` is expanded to a closed dynamic union of all valid pro

For example, given the closed dynamic type `BOOL | LIST<INT> | BOOLEAN | LIST<FLOAT | INT>`, the normalized type would be: `BOOLEAN | LIST<INTEGER | FLOAT>`.

This normalization is run on types used in xref::syntax/expressions.adoc#type-predicate-expressions[type predicate expressions], and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
This normalization is run on types used in xref::values-and-types/type-predicate.adoc[type predicate expressions], and in xref::constraints/examples.adoc#constraints-examples-node-property-type[node] and xref::constraints/examples.adoc#constraints-examples-relationship-property-type[relationship] property type constraints.
Type normalization is also used to ensure the consistency of the output for the xref::functions/scalar.adoc#functions-valueType[valueType()] function.

[[ordering-of-types]]
Expand Down