removing unique constraint for link based descriptor queries#215
Merged
removing unique constraint for link based descriptor queries#215
Conversation
Contributor
|
Target CPP Coverage: 64.3906% Target Python Coverage: 98.02% |
Contributor
Author
|
@cwlacewe well this is weird. It was a one line change and coverage hiccupped like that? |
Contributor
|
@ifadams, I noticed this. It's from your previous PR which needed additional testing. I created an issue I'm working on now (#213) |
Contributor
|
Target CPP Coverage: 63.9716% Target Python Coverage: 98.02% |
cwlacewe
approved these changes
Sep 11, 2024
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
2 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.
Quick fix here!
We had a requirement for a unique response internally from the database query, which for link-based FindDescriptor queries would obviously not be guaranteed.