Skip to content

Document relationship key and uniqueness constraints commands #175

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 2 commits into from
Jan 4, 2023
Merged

Document relationship key and uniqueness constraints commands #175

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
550c5f9
Update link
Hunterness Nov 25, 2022
6a4adcf
Change constraint name to node/relationship property uniqueness const…
Hunterness Dec 14, 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
6 changes: 3 additions & 3 deletions 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 @@ -506,7 +506,7 @@ The import command is run with the option `--stage=build`.
** _merge_ stage:
+
During this stage, the import tool merges the new with the existing data in the database.
It also updates the affected indexes and upholds the affected uniqueness constraints and property existence constraints.
It also updates the affected indexes and upholds the affected property uniqueness constraints and property existence constraints.
The import command is run with the option `--stage=merge` and the database must be stopped.

.Incremental import in a single command
Expand Down Expand Up @@ -793,7 +793,7 @@ The header contains information for each field, with the format `<name>:<field_t
The `<name>` is used for properties and node IDs.
In all other cases, the `<name>` part of the field is ignored.

When using incremental import, you will need to have node uniqueness constraints in place for the property key and label combinations that form the primary key, or the uniquely identifiable nodes.
When using incremental import, you will need to have node property uniqueness constraints in place for the property key and label combinations that form the primary key, or the uniquely identifiable nodes.
For example, importing nodes with a `Person` label that are uniquely identified with a `uuid` property key, the format of the header should be `uuid:ID{label:Person}`.

This is also true when working with multiple groups.
Expand All @@ -802,7 +802,7 @@ For example, you can use `uuid:ID(Person){label:Person}`, where the relationship
[NOTE]
====
* For more information on constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints[Cypher Manual -> Constraints].
* For examples of creating unique constraints, see link:{neo4j-docs-base-uri}/cypher-manual/{page-version}/constraints/examples/#administration-constraints-unique-nodes[Cypher Manual -> Unique node property 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].
====

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