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

Remove DROP from vulns creation #1281

Merged
merged 2 commits into from
Sep 1, 2020
Merged

Remove DROP from vulns creation #1281

merged 2 commits into from
Sep 1, 2020

Conversation

mattmundell
Copy link
Contributor

@mattmundell mattmundell commented Aug 31, 2020

This DROP was added in 01baac2, which changed the view to a UNION with
explicit columns. It's likely that the DROP was needed because CREATE OR
REPLACE does not support changing the columns.

But that was 2017 and the columns have not changed since, so anyone
upgrading from the last version will have the same columns.

If someone needs to change the columns they can add a migrator.

What:

Remove DROP from vulns creation.

Why:

We have reports of "ERROR: relation "vulns" does not exist" that are hard to reproduce, and this may help.

How:

Restart gvmd.

Checklist:

This DROP was added in 01baac2, which changed the view to a UNION with
explicit columns.  It's likely that the DROP was needed because CREATE OR
REPLACE does not support changing the columns.

But that was 2017 and the columns have not changed since, so anyone
upgrading from the last version will have the same columns.

If someone need to change the columns they can add a migrator.
@mattmundell mattmundell marked this pull request as ready for review August 31, 2020 19:36
Copy link
Contributor

@bjoernricks bjoernricks left a comment

Choose a reason for hiding this comment

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

Looks legit to me

@bjoernricks bjoernricks merged commit 41f4484 into gvmd-20.08 Sep 1, 2020
@cfi-gb cfi-gb deleted the remove-vulns-drop branch September 26, 2020 11:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants