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.

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

Add docs for using exclamation mark short hand in types #764

Merged
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,26 @@ This section lists all of the features that have been removed, deprecated, added
Replacement syntax for deprecated and removed features are also indicated.

[[cypher-deprecations-additions-removals-5.14]]
== Version 5.14
== Neo4j 5.14

=== Updated features

[cols="2", options="header"]
|===
| Feature
| Details
a|
label:functionality[]
label:updated[]

[source, cypher, role="noheader"]
----
IS :: INTEGER!
----

| Extended xref::values-and-types/property-structural-constructed.adoc#types-synonyms[type] syntax to allow an exclamation mark `!` as a synonym for `NOT NULL`.

|===

=== New features

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -105,6 +105,7 @@ However, not all types can be used in all places.
|===

All Cypher types contain the `null` value. To make them not nullable, `NOT NULL` can be appended to the end of the type (e.g. `BOOLEAN NOT NULL`, `LIST<FLOAT NOT NULL>`).
A shorthand syntax equivalent, introduced in Neo4j 5.14, for `NOT NULL` is to use an exclamation mark `!` (e.g. `INTEGER!`, `LIST<STRING!>`).
Note that closed dynamic types (`INNER_TYPE_1 | INNER_TYPE_2...`) cannot be appended with `NOT NULL`: all inner types must be nullable, or all appended with `NOT NULL`.

[[type-normalization]]
Expand Down