Skip to content

Change the project_id index to be unique on vulnerability_statistics

What does this MR do?

This MR changes the already existing index on project_id column of vulnerability_statistics table to be unique as we decided to store only the active vulnerability statistics in this table.

Migration Outputs

Up

== 20200702123805 ChangeProjectIdIndexToBeUniqueOnVulnerabilityStatisticsTable: migrating
-- remove_index(:vulnerability_statistics, :project_id)
   -> 0.0029s
-- add_index(:vulnerability_statistics, :project_id, {:name=>"index_vulnerability_statistics_on_unique_project_id", :unique=>true})
   -> 0.0020s
== 20200702123805 ChangeProjectIdIndexToBeUniqueOnVulnerabilityStatisticsTable: migrated (0.0050s)

Down

== 20200702123805 ChangeProjectIdIndexToBeUniqueOnVulnerabilityStatisticsTable: reverting
-- remove_index(:vulnerability_statistics, {:name=>"index_vulnerability_statistics_on_unique_project_id"})
   -> 0.0009s
-- add_index(:vulnerability_statistics, :project_id)
   -> 0.0024s
== 20200702123805 ChangeProjectIdIndexToBeUniqueOnVulnerabilityStatisticsTable: reverted (0.0035s)

Does this MR meet the acceptance criteria?

Conformity

Availability and Testing

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

  • [-] Label as security and @ mention @gitlab-com/gl-security/appsec
  • [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
  • [-] Security reports checked/validated by a reviewer from the AppSec team
Edited by Mehmet Emin INAC

Merge request reports

Loading