You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.adoc
+50-1Lines changed: 50 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,14 @@
1
1
= Neo4j Cypher Manual
2
2
3
+
This page covers the following topics:
4
+
5
+
* xref:README.adoc#building-locally[]
6
+
* xref:README.adoc#raising-prs[]
7
+
* xref:README.adoc#documenting-changes[]
8
+
* xref:README.adoc#cypher-gql[]
9
+
10
+
11
+
[[building-locally]]
3
12
== Building locally
4
13
5
14
=== Prereqs
@@ -39,7 +48,7 @@ When you run `npm start`, the project is monitored for updates to asciidoc files
39
48
40
49
If a change to an asciidoc file is detected, the site is automatically rebuilt.
41
50
42
-
51
+
[[raising-prs]]
43
52
== Raising PRs
44
53
45
54
@@ -68,3 +77,43 @@ There are a few edge cases where we might want to work only on the current branc
68
77
** Create a feature branch from `dev`, to be merged into `dev` when appropriate.
69
78
* When a new version is ready to published, the `5.x` branch will get a git tag, named with the exact version (for example, **5.1.0**), signifying that this point-in-time marks the completion of the work for that minor release.
70
79
* Updates merged into the `dev` branch for the next release are cherry-picked into the `5.x` branch.
80
+
81
+
[[documenting-changes]]
82
+
== Documenting changes to Cypher
83
+
84
+
New, updated, deprecated, and removed features must be recorded on the xref:modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc[Deprecations, additions, and compatibility] page.
85
+
86
+
New and deprecated features should also be marked with a label:
87
+
88
+
* If the impacted feature has its own header in the Cypher Manual, use the following:
89
+
90
+
....
91
+
[role=label--new-5.x]
92
+
== Header
93
+
....
94
+
95
+
....
96
+
[role=label--deprecated]
97
+
== Header
98
+
....
99
+
100
+
* If the impacted feature is documented within a table (such as a return column in a `SHOW` command), use the following:
101
+
102
+
`featureX` label:new[Introduced in 5.x] +
103
+
`featureY` label:deprecated[]
104
+
105
+
Labels can be difficult to apply to updated features.
106
+
In these cases, it is often preferable to note the change in a sentence.
107
+
For example: "As of Neo4j 5.x, `featureX` supports ..."
108
+
109
+
Removed features should be deleted from the Cypher Manual.
110
+
111
+
[[cypher-gql]]
112
+
== Cypher and GQL
113
+
114
+
When documenting a new Cypher feature, its relationship with GQL must be considered:
115
+
116
+
* If the feature is part of GQL's mandatory features, it should be recorded on the page xref:modules/ROOT/pages/appendix/gql-conformance/supported-mandatory.adoc[Supported mandatory GQL features].
117
+
* If the feature is part of GQL's optional features, it should be recorded on the page xref:modules/ROOT/pages/appendix/gql-conformance/supported-optional.adoc[Supported optional GQL features].
118
+
* if the feature adds functionality for which there exists an analogous, optional GQL feature, it should be recorded on the page xref:modules/ROOT/pages/appendix/gql-conformance/analogous-cypher.adoc[Optional GQL features and analogous Cypher].
119
+
* If the feature adds functionality for which there exists no GQL equivalent, it should be recorded on the page xref:modules/ROOT/pages/appendix/gql-conformance/additional-cypher.adoc[Additional Cypher features].
| "The catchup protocol times out if the given duration elapses with no network activity. Every message received by the client from the server extends the timeout duration."
199
+
| "server.backup.enabled"
200
+
| "true"
201
+
| "Enable support for running online backups."
202
202
203
-
| "dbms.cluster.discovery.endpoints"
204
-
| null
205
-
| "A comma-separated list of endpoints that a server should contact in order to discover other cluster members. Typically, all cluster members, including the current server, must be specified in this list. The setting configures the endpoints for Discovery service V1."
See link:{neo4j-docs-base-uri}/operations-manual/current/backup-restore/restore-dump/#load-dump-cloud-storage[Operations Manual -> Load a dump from a cloud storage] on how to set up access to cloud storages.
@@ -994,60 +993,6 @@ SHOW INDEXES WHERE owningConstraint IS NOT NULL
994
993
[NOTE]
995
994
Property existence and property type constraints are not backed by indexes.
996
995
997
-
[[create-constraint-with-index-provider]]
998
-
==== Creating constraints with an index provider
999
-
1000
-
Because property uniqueness and key constraints have backing indexes, an index provider can be provided when creating these constraints using the `OPTIONS` clause and the `indexProvider` option.
1001
-
1002
-
The only valid value for the index provider is:
1003
-
1004
-
* `range-1.0` label:default[]
1005
-
1006
-
1007
-
.Create a node key constraint with a specified index provider
1008
-
======
1009
-
1010
-
.Create a constraint requiring `Actor` nodes to have a unique `surname` property as a node key, specifying `range-1.0` as index provider
1011
-
[source, cypher]
1012
-
----
1013
-
CREATE CONSTRAINT constraint_with_provider
1014
-
FOR (actor:Actor) REQUIRE actor.surname IS NODE KEY
1015
-
OPTIONS {
1016
-
indexProvider: 'range-1.0'
1017
-
}
1018
-
----
1019
-
1020
-
.Result
1021
-
[source, queryresult]
1022
-
----
1023
-
Added 1 constraint.
1024
-
----
1025
-
1026
-
======
1027
-
1028
-
.Create a relationship property uniqueness constraint with a specified index provider
1029
-
======
1030
-
1031
-
.Create a constraint requiring `SEQUEL_OF` relationships to have a unique combination of `order`, `seriesTitle`, and `number` properties, specifying `range-1.0` as index provider
1032
-
[source, cypher]
1033
-
----
1034
-
CREATE CONSTRAINT rel_constraint_with_options
1035
-
FOR ()-[sequel:SEQUEL_OF]-() REQUIRE (sequel.order, sequel.seriesTitle, sequel.number) IS UNIQUE
1036
-
OPTIONS {
1037
-
indexProvider: 'range-1.0'
1038
-
}
1039
-
----
1040
-
1041
-
.Result
1042
-
[source, queryresult]
1043
-
----
1044
-
Added 1 constraint.
1045
-
----
1046
-
1047
-
======
1048
-
1049
-
There are no valid index configuration values for the constraint-backing range indexes.
0 commit comments