Skip to content

Update constraints link following restructure in Cypher Manual #1874

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 1 commit into from
Oct 17, 2024
Merged

Update constraints link following restructure in Cypher Manual #1874

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
2 changes: 1 addition & 1 deletion modules/ROOT/pages/database-internals/concurrent-data-access.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ The easiest way to work around this is to only read each property once, and keep
=== Missing and double reads

When scanning an xref:performance/index-configuration.adoc[index], entities may be observed multiple times or skipped entirely, even if they are present in the index.
This is true even for indexes that back link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/examples/#constraints-examples-node-uniqueness[uniqueness constraints].
This is true even for indexes that back link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/managing-constraints/#create-property-uniqueness-constraints[property uniqueness constraints].

During the scan, if another concurrent query changes an entity's property to a position ahead of the scan, the entity might appear again in the index.
Similarly, the entity may not appear at all if the property is changed to a previously scanned position.
Expand Down
2 changes: 1 addition & 1 deletion modules/ROOT/pages/database-internals/store-formats.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ For example:
bin/neo4j-admin database copy --to-format="block" mydb blockdb --copy-schema
----
. After the successful completion, start the database using the Cypher command `START DATABASE mydb`.
Indexes are populated the first time the database is started, which might take some time if there are uniqueness constraints.
Indexes are populated the first time the database is started, which might take some time if there are property uniqueness constraints.

[[change-store-format-cluster]]
==== In a cluster
Expand Down
2 changes: 1 addition & 1 deletion modules/ROOT/pages/tools/neo4j-admin/neo4j-admin-import.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -976,7 +976,7 @@ This is also true when working with multiple groups.
For example, you can use `uuid:ID(Person){label:Person}`, where the relationship CSV data can refer to different groups for its `:START_ID` and `:END_ID`, just like the full import method.

* For more information on constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints[Cypher Manual -> Constraints].
* For examples of creating property uniqueness constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/examples/#constraints-examples-node-uniqueness[Cypher Manual -> Node property uniqueness constraints].
* For examples of creating property uniqueness constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/managing-constraints/#create-property-uniqueness-constraints[Cypher Manual -> Create property uniqueness constraints].
====

[[import-tool-header-format-nodes]]
Expand Down