Skip to content

5.0 remove drop constraint by schema #9

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

Merged
merged 4 commits into from
Jul 21, 2022
Merged

5.0 remove drop constraint by schema #9

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2183db5
Remove DROP CONSTRAINT ON examples
martin-neotech Jul 20, 2022
c62f0a1
Removed query plans
martin-neotech Jul 20, 2022
a6366c2
Review comment
martin-neotech Jul 21, 2022
442c38f
delta page for 5.0
martin-neotech Jul 21, 2022
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
116 changes: 0 additions & 116 deletions modules/ROOT/pages/constraints/examples.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1207,15 +1207,11 @@ To get all columns, use `+SHOW INDEXES YIELD * WHERE ...+`.
== Deprecated syntax

* xref::constraints/examples.adoc#administration-constraints-create-a-unique-constraint-using-deprecated-syntax[]
* xref::constraints/examples.adoc#administration-constraints-drop-a-unique-constraint[]
* xref::constraints/examples.adoc#administration-constraints-create-a-node-property-existence-constraint-using-deprecated-syntax-1[]
* xref::constraints/examples.adoc#administration-constraints-create-a-node-property-existence-constraint-using-deprecated-syntax-2[]
* xref::constraints/examples.adoc#administration-constraints-drop-a-node-property-existence-constraint[]
* xref::constraints/examples.adoc#administration-constraints-create-a-relationship-property-existence-constraint-using-deprecated-syntax-1[]
* xref::constraints/examples.adoc#administration-constraints-create-a-relationship-property-existence-constraint-using-deprecated-syntax-2[]
* xref::constraints/examples.adoc#administration-constraints-drop-a-relationship-property-existence-constraint[]
* xref::constraints/examples.adoc#administration-constraints-create-a-node-key-constraint-using-deprecated-syntax[]
* xref::constraints/examples.adoc#administration-constraints-drop-a-node-key-constraint[]


[discrete]
Expand Down Expand Up @@ -1246,34 +1242,6 @@ Unique constraints added: 1
======


[discrete]
[[administration-constraints-drop-a-unique-constraint]]
=== Drop a unique constraint
Copy link
Collaborator

@Hunterness Hunterness Jul 22, 2022

Choose a reason for hiding this comment

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

I still think you're missing removing things in the .../constraints/syntax.adoc file

Copy link
Contributor Author

@martin-neotech martin-neotech Jul 22, 2022

Choose a reason for hiding this comment

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

@Hunterness #16


By using `DROP CONSTRAINT`, a B-tree index-backed unique constraint is removed from the database.


.+DROP CONSTRAINT+
======

.Query
[source, cypher, indent=0]
----
DROP CONSTRAINT ON (book:Book) ASSERT book.isbn IS UNIQUE
----

.Result
[queryresult]
----
+-------------------+
| No data returned. |
+-------------------+
Unique constraints removed: 1
----

======


[discrete]
[[administration-constraints-create-a-node-property-existence-constraint-using-deprecated-syntax-1]]
=== Create a node property existence constraint using deprecated syntax 1
Expand Down Expand Up @@ -1330,34 +1298,6 @@ Property existence constraints added: 1
======


[discrete]
[[administration-constraints-drop-a-node-property-existence-constraint]]
=== Drop a node property existence constraint

By using `DROP CONSTRAINT`, a node property existence constraint is removed from the database.


.+DROP CONSTRAINT+
======

.Query
[source, cypher, indent=0]
----
DROP CONSTRAINT ON (book:Book) ASSERT exists(book.isbn)
----

.Result
[queryresult]
----
+-------------------+
| No data returned. |
+-------------------+
Property existence constraints removed: 1
----

======


[discrete]
[[administration-constraints-create-a-relationship-property-existence-constraint-using-deprecated-syntax-1]]
=== Create a relationship property existence constraint using deprecated syntax 1
Expand Down Expand Up @@ -1414,34 +1354,6 @@ Property existence constraints added: 1
======


[discrete]
[[administration-constraints-drop-a-relationship-property-existence-constraint]]
=== Drop a relationship property existence constraint

To remove a relationship property existence constraint from the database, use `DROP CONSTRAINT`.


.+DROP CONSTRAINT+
======

.Query
[source, cypher, indent=0]
----
DROP CONSTRAINT ON ()-[like:LIKED]-() ASSERT exists(like.day)
----

.Result
[queryresult]
----
+-------------------+
| No data returned. |
+-------------------+
Property existence constraints removed: 1
----

======


[discrete]
[[administration-constraints-create-a-node-key-constraint-using-deprecated-syntax]]
=== Create a node key constraint using deprecated syntax
Expand Down Expand Up @@ -1469,31 +1381,3 @@ Node key constraints added: 1

======


[discrete]
[[administration-constraints-drop-a-node-key-constraint]]
=== Drop a node key constraint

Use `DROP CONSTRAINT` to remove a B-tree index-backed node key constraint from the database.


.+DROP CONSTRAINT+
======

.Query
[source, cypher, indent=0]
----
DROP CONSTRAINT ON (n:Person) ASSERT (n.firstname, n.surname) IS NODE KEY
----

.Result
[queryresult]
----
+-------------------+
| No data returned. |
+-------------------+
Node key constraints removed: 1
----

======

53 changes: 52 additions & 1 deletion modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,8 +35,59 @@ The ability to dropp an index based on the schema has been removed.

Use the command to drop an index by the name of the index instead, `DROP INDEX index_name`.

|===

a|
label:functionality[]
label:removed[]
[source, cypher, role="noheader", indent=0]
----
DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS NODE KEY
Copy link
Collaborator

@Hunterness Hunterness Jul 22, 2022

Choose a reason for hiding this comment

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

In the version we added before, we had all drop command in one place:

a|
label:functionality[]
label:removed[]
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS NODE KEY
----
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS UNIQUE
----
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON (n:Label) ASSERT exists(n.prop)
----
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON ()-[r:Type]-() ASSERT exists(r.prop)
----
a|
Replaced by:
[source, cypher, role="noheader"]
----
DROP CONSTRAINT name
----

so instead of having 4 entries we had one, cause it's the same functionality that has been removed

a|
label:functionality[]
label:removed[]
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS NODE KEY
----
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS UNIQUE
----
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON (n:Label) ASSERT exists(n.prop)
----
[source, cypher, role="noheader"]
----
DROP CONSTRAINT ON ()-[r:Type]-() ASSERT exists(r.prop)
----
a|
The ability to dropp a constraint based on the schema has been removed.

Use the command to drop a constraint by the name of the constraint instead, `DROP CONSTRAINT constraint_name`.
----

----
a|
The ability to dropp a constraint based on the schema has been removed.

Use the command to drop a constraint by the name of the constraint instead, `DROP CONSTRAINT constraint_name`.


a|
label:functionality[]
label:removed[]
[source, cypher, role="noheader", indent=0]
----
DROP CONSTRAINT ON (n:Label) ASSERT (n.prop) IS UNIQUE
----
a|
The ability to dropp a constraint based on the schema has been removed.

Use the command to drop a constraint by the name of the constraint instead, `DROP CONSTRAINT constraint_name`.


a|
label:functionality[]
label:removed[]
[source, cypher, role="noheader", indent=0]
----
DROP CONSTRAINT ON (n:Label) ASSERT exists(n.prop)
----
a|
The ability to dropp a constraint based on the schema has been removed.

Use the command to drop a constraint by the name of the constraint instead, `DROP CONSTRAINT constraint_name`.


a|
label:functionality[]
label:removed[]
[source, cypher, role="noheader", indent=0]
----
DROP CONSTRAINT ON ()-[r:Type]-() ASSERT exists(r.prop)
----
a|
The ability to dropp a constraint based on the schema has been removed.

Use the command to drop a constraint by the name of the constraint instead, `DROP CONSTRAINT constraint_name`.

|===

// === Deprecated features

Expand Down
24 changes: 0 additions & 24 deletions modules/ROOT/pages/execution-plans/operator-summary.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -196,30 +196,6 @@ Tests for the absence of a pattern predicate.
| label:yes[]
|

| xref::execution-plans/operators.adoc#query-plan-drop-node-key-constraint[DropNodeKeyConstraint]
| Drops a node key constraint from a set of properties for all nodes with a certain label.
| label:yes[]
| label:yes[]
| label:deprecated[]

| xref::execution-plans/operators.adoc#query-plan-drop-node-property-existence-constraint[DropNodePropertyExistenceConstraint]
| Drops an existence constraint from a property for all nodes with a certain label.
| label:yes[]
| label:yes[]
| label:deprecated[]

| xref::execution-plans/operators.adoc#query-plan-drop-relationship-property-existence-constraint[DropRelationshipPropertyExistenceConstraint]
| Drops an existence constraint from a property for all relationships of a certain type.
| label:yes[]
| label:yes[]
| label:deprecated[]

| xref::execution-plans/operators.adoc#query-plan-drop-unique-constraint[DropUniqueConstraint]
| Drops a unique constraint from a set of properties for all nodes with a certain label.
| label:yes[]
| label:yes[]
| label:deprecated[]

| xref::execution-plans/operators.adoc#query-plan-eager[Eager]
| For isolation purposes, `Eager` ensures that operations affecting subsequent operations are executed fully for the whole dataset before continuing execution.
|
Expand Down
Loading