Document relationship key and uniqueness constraints #225
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hunterness
added
new
Collaborator
|
Looks like you've updated the documentation! Check out your changes at https://neo4j-docs-cypher-225.surge.sh |
l-heemann
requested changes
Nov 23, 2022
Contributor
l-heemann
left a comment
l-heemann
left a comment
There was a problem hiding this comment.
Seems like we have copied over wierd choices from the node constraints section into the relationship constraints section. This is probably not the PR/task for cleaning up existing documentation, so maybe we should leave that as a separate task?
I have added comments on the parts that stuck out the most in the new section.
Hunterness
force-pushed
the
5.3-relationship-constraints
branch
from
d5e6edb to
d10ac4a
Compare
Hunterness
commented
Nov 25, 2022
emmaholmbergohlsson
approved these changes
Dec 5, 2022
Contributor
emmaholmbergohlsson
left a comment
emmaholmbergohlsson
left a comment
There was a problem hiding this comment.
Looks good to me, just spotted a small thing
Hunterness
force-pushed
the
5.3-relationship-constraints
branch
from
e0dbe70 to
4bae968
Compare
Hunterness
force-pushed
the
5.3-relationship-constraints
branch
from
2c206d6 to
1a0c0bb
Compare
modules/ROOT/pages/deprecations-additions-removals-compatibility.adoc
Outdated
Show resolved
Hide resolved
Hunterness
commented
Dec 20, 2022
Hunterness
force-pushed
the
5.3-relationship-constraints
branch
2 times, most recently
from
a146d9d to
5072886
Compare
Hunterness
force-pushed
the
5.3-relationship-constraints
branch
from
5072886 to
0a6e270
Compare
and also allowing `UNIQUENESS` for the type filtering in `SHOW UNIQUE CONSTRAINTS`
It was a mix of uniqueness, unique and unique property
Also remove 2 places referencing the now removed `db.indexes` and `db.constraints` procedures
…raints after discussion with Valerio and Emma
Co-authored-by: Jens Pryce-Åklundh <112686610+JPryce-Aklundh@users.noreply.github.com>
Hunterness
force-pushed
the
5.3-relationship-constraints
branch
from
0a6e270 to
0b72db8
Compare
recrwplay
pushed a commit
that referenced
this pull request
Jan 25, 2023
Feature merged in 5.3 but hidden behind feature flag, the flag was turned true by default in 5.4.
lidiazuin
pushed a commit
to lidiazuin/docs-cypher
that referenced
this pull request
May 21, 2025
Feature merged in 5.3 but hidden behind feature flag, the flag was turned true by default in 5.4.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature merged in 5.3 but hidden behind feature flag so documentation should probably not be merged until that is removed, flag turned true by default in https://github.com/neo-technology/neo4j/pull/18469, so can go in once that is merged. Feature flag has been merged and is turned on from 5.4.
Also added to the cheat sheet here (also updates links): https://github.com/neo4j/docs-cheat-sheet/pull/40
And updates links in operations manual here: neo4j/docs-operations#175