Repository navigation
Use Neo4j 5+ syntax for uniqueness constraints - #563
Open
rogermyung wants to merge 1 commit into
Open
rogermyung wants to merge 1 commit into
rogermyung wants to merge 1 commit into
Conversation
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The ON ... ASSERT form of CREATE CONSTRAINT was removed in Neo4j 5, so every constraint statement failed against modern servers. The failure is swallowed by create_constraints, which logs it and continues, leaving loads with no unique index on id and turning every node MERGE and edge MATCH into a full label scan.
Switch to the FOR ... REQUIRE form and update the unit test that asserted on the old string.