Skip to content

Transition sbom_occurrences to loose foreign keys

What does this MR do and why?

This MR is the first step in the decomposition of the sbom_occurrences table to the new gitlab_sec schema as part of the sec db decomposition.

The idea is to keep the change set minimal, identify cross join issues to be worked moving forward, and configure loose foreign keys for relationships that will go beyond the bounds of a single DB. (EG: sbom_occurrences -> projects).

Because sbom_occurrences has a high number of foreign keys to other tables within scope of this slice of decomposition we can drop a number of previous cross-DB join and transaction allowances in scope of this 🎉

Please see the new FAQ on the parent epic for some common review questions

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Lucas Charles

Merge request reports

Loading