Let Timeline handle non-existing bugs #780
Merged
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
If an history entry refers to a bug that does not exist in the database, history_get_event_from_row() throws application error 1100. Even though it is not a normal situation to find orphan records in the history table, the overhead of verifying a bug's existence at the beginning of the loop is negligible, so it doesn't hurt to add the extra bug_exists() check. Fixes #20727
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.
If an history entry refers to a bug that does not exist in the database, history_get_event_from_row() throws application error 1100.
Even though it is not a normal situation to find orphan records in the history table, the overhead of verifying a bug's existence at the beginning of the loop is negligible, so it doesn't hurt to add the extra bug_exists() check.
Fixes #20727