fix: Also catch Neo.ClientError.Schema.ConstraintAlreadyExists while locking.
#324
Conversation
This file contains 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
…e locking. A `Neo4jException` is thrown with the code `Neo.ClientError.Schema.ConstraintAlreadyExists` when a constraint already exists that is not only equivalent but has a name. The same scenario might happen in an upgrade from 4.3 to 4.4. at least, as there the mechanism that decides which constraints are equivalent seems to have changed. Thanks to @ali-ince for reporting this and help me fixing it.
|
Kudos, SonarCloud Quality Gate passed! |
michael-simons
deleted the
issue/catch-all-codes-indicating-existing-constraint
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A
Neo4jExceptionis thrown with the codeNeo.ClientError.Schema.ConstraintAlreadyExistswhen a constraint already exists that is not only equivalent but has a name.The same scenario might happen in an upgrade from 4.3 to 4.4. at least, as there the mechanism that decides which constraints are equivalent seems to have changed.
Thanks to @ali-ince for reporting this and help me fixing it.