-
- Downloads
Synchronously add indexes for new `vulnerability_occurrences` cols
We want to drop the `vulnerability_occurrence_pipelines` table. In order to do this, we still need the first and latest pipeline ID stored somewhere to support the existing feature-set The columns and asynchronous index creation were added in a [previous MR][0] This change adds the synchronous index migration to complete the index creation [process][1] Follow-up Work --------------------------- We will need to add loose foreign keys and model association. Both of these are blocked on this index creation That work is tracked in the following tasks: - #443283 - #443284 --- Related to #422382 Resolves #443282 [0]:!144697 [1]:https://docs.gitlab.com/ee/development/database/adding_database_indexes.html#create-indexes-asynchronously Changelog: added
Showing
- db/post_migrate/20240226072310_prepare_index_for_initial_and_latest_pipeline_id_to_vulnerability_occurrences.rb 1 addition, 1 deletion...al_and_latest_pipeline_id_to_vulnerability_occurrences.rb
- db/post_migrate/20240226094324_add_index_for_initial_and_latest_pipeline_id_to_vulnerability_occurrences.rb 21 additions, 0 deletions...al_and_latest_pipeline_id_to_vulnerability_occurrences.rb
- db/schema_migrations/20240226094324 1 addition, 0 deletionsdb/schema_migrations/20240226094324
- db/structure.sql 4 additions, 0 deletionsdb/structure.sql
db/schema_migrations/20240226094324
0 → 100644
Please register or sign in to comment