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

Added a new modification_time column to reports #1513

Merged

Conversation

jhelmold
Copy link
Member

@jhelmold jhelmold commented May 7, 2021

What:
Added the new function "migrate_243_to_244 ()" in manage_migrators.c to add
the new column "modification_time" to the "reports" table.

Adjusted GVMD_DATABASE_VERSION in CMakelists.txt.

Adjusted the corresponding entries in the REPORT_ITERATOR_COLUMNS in
manage_sql.c.

Added update of modification_time for reports during scans.

Why:
Make report timestamps more consistent.

How did you test it:
Checked reports and report filters.

Checklist:

jhelmold and others added 6 commits May 7, 2021 14:27
Added the new function "migrate_243_to_244 ()" in manage_migrators.c to add
the new column "modification_time" to the "reports" table.

Adjusted GVMD_DATABASE_VERSION in CMakelists.txt

Adjusted the corresponding entries in the REPORT_ITERATOR_COLUMNS in
manage_sql.c
Update modification_time when status is changed and when new results
are received from scanner
Created new function "update_report_modification_time ()" and used
it in "cve_scan_host ()" to update the modification_time during
CVE scans.
@jhelmold jhelmold marked this pull request as ready for review May 10, 2021 13:14
@jhelmold jhelmold requested a review from a team as a code owner May 10, 2021 13:14
@timopollmeier timopollmeier merged commit 0277844 into greenbone:master May 11, 2021
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