Added a new modification_time column to reports #1513
Merged
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.
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: