Fix vulndb column name in getVulnerabilityAliases method #2428
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.
Signed-off-by: mehab [email protected]
Description
This change is updating the column name for getting vulnerability aliases from vulndb
Current behaviour
The current query for getting vulnerability aliases for vulndb as source in the getVulnerabilityAliases method is
query = pm.newQuery(VulnerabilityAlias.class, "vulnDb== :vulnDb");
which has column name invalid.Expected behaviour
The correct id column for vulndb id is vulnDbId and thus the query should be
query = pm.newQuery(VulnerabilityAlias.class, "vulnDbId == :vulnDb");
so that there is no error.Addressed Issue
Additional Details
Checklist