Fix insertions in table mri_violations_log #1291
Merged
Conversation
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
nicolasbrossard
added
Perl imaging pipeline
Difficulty: Simple
MaximeBICMTL
pushed a commit
to maximemulder/Loris-MRI
that referenced
this pull request
Jun 16, 2025
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.
When one of the protocol checks fails, the MRI pipeline attempts to save a record in table
mri_violations_logbut an error message is printed saying that columnCandIDdoes not exist (the dreaded candidate ID refactoring...) This PR updates the MySQL insertion statement so that it usesCandidateIDinstead ofCandIDwhen inserting inmri_violations_log.