Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pgsql: Do not insert entry in Vulnerability_FixedIn_Feature if existing #263

Merged
merged 2 commits into from
Nov 13, 2016

Conversation

Quentin-M
Copy link
Contributor

Fixes #238

@Quentin-M
Copy link
Contributor Author

When this PR lands, it should be backported to the stable branch(es).

)
SELECT 'exi', id FROM Vulnerability_FixedIn_Feature WHERE vulnerability_id = $1 AND feature_id = $2
UNION
SELECT 'new', id FROM new_fixedinfeature`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's change this first value to be a boolean and bind it to a Go variable named "created" at the callsite.

@jzelinskie
Copy link
Contributor

We really need to break the database tests into different functions that describe the scenario they're testing rather than having one giant monolithic function for each method in the interface.

@Quentin-M
Copy link
Contributor Author

@jzelinskie #264 + ec0aad9. Thank you!

@jzelinskie
Copy link
Contributor

LGTM. I set a reminder to backport these changes on Monday.

@Quentin-M Quentin-M merged commit 7fddd68 into quay:master Nov 13, 2016
@Quentin-M Quentin-M deleted the rhel_unique_fixedin branch November 13, 2016 12:25
jzelinskie pushed a commit that referenced this pull request Nov 14, 2016
pgsql: Do not insert entry in Vulnerability_FixedIn_Feature if existing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug things are not as they seem
Development

Successfully merging this pull request may close these issues.

None yet

2 participants