Skip to content

Commit 462834c

Browse files
post-review corrections 2 (syntax page)
1 parent 5f55cae commit 462834c

File tree

9 files changed

+52
-55
lines changed

9 files changed

+52
-55
lines changed

modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ ALTER CURRENT GRAPH DROP {
137137
}
138138
----
139139

140-
| Introduced the ability to drop elements from graph types using the `ALTER CURRENT GRAPH TYPE DROP` command.
140+
| Introduced the ability to drop element types and constraints from graph types using the `ALTER CURRENT GRAPH TYPE DROP` command.
141141
For more information, see xref:schema/graph-types/drop-graph-type-elements.adoc[].
142142
|===
143143

modules/ROOT/pages/schema/constraints/drop-constraints.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -77,12 +77,12 @@ Removed 1 constraint.
7777
Constraints that are created as part of xref:schema/graph-types/set-graph-types.adoc#node-element-types[node] or xref:schema/graph-types/set-graph-types.adoc#relationship-element-types[relationship element types] in a xref:schema/graph-types/index.adoc[graph type] cannot be dropped with the `DROP CONSTRAINT constraint_name` command.
7878
This includes the following constraints:
7979
80-
* Property existence and property type constraints on identifying labels or relationship types
80+
* Property existence and property type constraints on identifying node labels or relationship types
8181
* Node label existence constraints
8282
* Relationship source and target label constraints
8383
8484
These constraints can only be dropped by dropping the full node or relationship element type.
85-
For more information, see xref:schema/graph-types/drop-graph-type-elements.adoc#drop-element-types[Drop node and relationship element types]
85+
For more information, see xref:schema/graph-types/drop-graph-type-elements.adoc#drop-element-types[Drop node and relationship element types].
8686
====
8787

8888
[[drop-constraint-with-parameter]]

modules/ROOT/pages/schema/constraints/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ The following constraints are available in Neo4j:
1111
* xref:schema/constraints/create-constraints.adoc#create-property-type-constraints[Property type constraints]: ensure that a property has the required property type for all nodes with a specific label or for all relationships with a specific type. label:enterprise-edition[]
1212
* xref:schema/constraints/create-constraints.adoc#create-key-constraints[Key constraints]: ensure that all properties exist and that the combined property values are unique for all nodes with a specific label or all relationships with a specific type.label:enterprise-edition[]
1313
14-
For more information index-backed constraints, constraint creation failures and data violation scenarios, as well as listing and dropping constraints, see:
14+
For more information about index-backed constraints, constraint creation failures and data violation scenarios, as well as creating, listing and dropping constraints, see:
1515

1616
* xref:schema/constraints/create-constraints.adoc[]
1717
* xref:schema/constraints/list-constraints.adoc[]

modules/ROOT/pages/schema/constraints/list-constraints.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -273,7 +273,7 @@ The list returned will only include a single value (the name of the constrained
273273
| LIST<STRING>
274274

275275
| enforcedLabel
276-
| The implied labels required by a node label existence constraint or the source node and target node labels required by a relationship source or target label constraint. label:default-output[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
276+
| The implied labels required by a node label existence constraint or the source node and target node labels required by a relationship source or target label constraint, or `null` for other constraints which do not constrain labels. label:default-output[] label:cypher[Cypher 25 only] label:new[Introduced in Neo4j 2025.xx]
277277
| STRING
278278

279279
| ownedIndex

modules/ROOT/pages/schema/graph-types/alter-graph-types.adoc

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,12 @@
22
:page-role: cypher-25-only new-neo4j-2025.xx enterprise-edition
33
= Alter graph types
44

5-
A graph type can be altered using the `ALTER CURRENT GRAPH TYPE ALTER` command.
6-
This command is used to modify existing xref:schema/graph-types/set-graph-types.adoc#node-element-types[node] and xref:schema/graph-types/set-graph-types.adoc#relationship-element-types[relationship element types] in a graph type.
5+
The xref:schema/graph-types/set-graph-types.adoc#node-element-types[node] and xref:schema/graph-types/set-graph-types.adoc#relationship-element-types[relationship element types] in a graph type can be altered using the `ALTER CURRENT GRAPH TYPE ALTER` command.
76
When altering a graph type, only those node or relationship element types to be modified should be included.
87

98
[NOTE]
109
====
11-
Setting a graph type requires the following privileges:
10+
Altering element types in a graph type requires the following privileges:
1211
1312
* link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`CREATE CONSTRAINT`]
1413
* link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`DROP CONSTRAINT`]

modules/ROOT/pages/schema/graph-types/drop-graph-type-elements.adoc

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
:description: Information about dropping elements in a graph type.
22
:page-role: cypher-25-only new-neo4j-2025.xx enterprise-edition
3-
= Drop elements in a graph type
3+
= Drop graph type elements
44

5-
The `ALTER CURRENT GRAPH TYPE DROP` command allows you to drop elements from a graph type.
5+
The `ALTER CURRENT GRAPH TYPE DROP` command allows you to drop element types and constraints from a graph type.
66

77
[NOTE]
8-
Dropping elements from a graph type the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`DROP CONSTRAINT` privilege].
8+
Dropping element types and constraints from a graph type the link:{neo4j-docs-base-uri}/operations-manual/current/authentication-authorization/database-administration/#access-control-database-administration-constraints[`DROP CONSTRAINT` privilege].
99

1010
.Set graph type
1111
[source, cypher]
@@ -28,7 +28,7 @@ ALTER CURRENT GRAPH TYPE SET {
2828
[[drop-element-types]]
2929
== Drop node and relationship element types
3030

31-
To fully drop a node or relationship element type, it is only necessary to define its identifying node label/relationship type appended with `\=>`.
31+
To fully drop a xref:schema/graph-types/set-graph-types.adoc#node-element-types[node] or xref:schema/graph-types/set-graph-types.adoc#relationship-element-types[relationship element type], it is only necessary to define its identifying node label/relationship type appended with `\=>`.
3232

3333
.Drop node and relationship element types
3434
[source, cypher]

modules/ROOT/pages/schema/graph-types/index.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@
55
Graph types allow you to specify a graph schema for a database.
66

77
When a database is created, it has an empty graph type, meaning it is free from any constraints on what can be stored in a database.
8-
Creating a graph type, typically done following the creation of a database, enables users to impose a schema on the nodes, relationships, and properties included in the graph type, thereby ensuring the integrity and quality of the data in a graph.
8+
Setting a graph type, typically done following the creation of a database, enables users to impose a schema on the nodes, relationships, and properties included in the graph type, thereby ensuring the integrity and quality of the data in a graph.
99

1010
Cypher supports open graph types, meaning that a graph type only constrains the data included by the graph type.
1111
It does not impose any constraints on nodes, relationships, and properties not included by the graph type.

modules/ROOT/pages/schema/graph-types/list-graph-types.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,8 +61,8 @@ Regardless of which syntax was used to define a property uniqueness or key const
6161

6262
To only return the graph type `specification`, use the command `SHOW CURRENT GRAPH TYPE YIELD specification`.
6363

64-
[[return-columns]]
65-
== Return columns for `SHOW CURRENT GRAPH TYPE`
64+
[[result-columns]]
65+
== Result columns for `SHOW CURRENT GRAPH TYPE`
6666

6767
There are two return columns for `SHOW CURRENT GRAPH TYPE`: `type` and `specification`.
6868
Both are returned by default.

0 commit comments

Comments
 (0)