Fix get diff hashes for new bugs #1259
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 the user tries to get diff hashes for new bugs, where no bugs found in the plist files gets an error message in case of pgsql because empty array is given to the pgsql `unnest` function. This commit solves this problem by returning an empty list.
csordasmarton
force-pushed
the
empty_new_hash_fix
branch
from
41f9867 to
599adf7
Compare
gyorb
approved these changes
Dec 14, 2017
Xazax-hun
approved these changes
Dec 16, 2017
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 the user tries to get diff hashes for new bugs, where no bugs found in the plist files gets an error message in case of pgsql because empty array is given to the pgsql
unnestfunction. This commit solves this problem by returning an empty list.