fix(ontology): existing cardinalities get duplicated in the triplestore when adding a new cardinality to a class (DEV-937) #2092
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.
Resolves DEV-937
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When adding a new cardinality to a resource class, all existing cardinalities of that class get duplicated in the triplestore. (Only visible in the triplestore, not in the API.)
Issue Number: DEV-937
What is the new behavior?
Cardinalities don't get duplicated.
Does this PR introduce a breaking change?
Other information