Parentage dam mismatch in Colony alert#1643
Merged
kollil merged 2 commits intorelease25.7-SNAPSHOTfrom Feb 25, 2026
Merged
Conversation
Parentage Dam mismatch records
brentlogan
approved these changes
Feb 25, 2026
Collaborator
brentlogan
left a comment
brentlogan
left a comment
There was a problem hiding this comment.
I'm approving this PR with the understanding that we'll confer with Raymond about the assumed rare edge case of ignored multiple genetic dams caused by the MAX aggregate functions in lines 26 and 37 in ParentageDamMismatch.sql.
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.
Added Parentage dam mismatch report in colony alert.