Add not null and delete cascade constraints on project_namespace_id
What does this MR do and why?
This MR introduces a not null
constraint for project_namespace_id
on projects
table as we want to ensure every project has a corresponding project namespace. Also it adds the cascade delete
FK on project_namespace_id
column.
This migration has to be run after !83587 (merged) i.e. its timestamps(20220326161803
and 20220326163653
) have to be after !83587 (merged) timestamp (20220324081709
)
!78046 (merged) re #354616 (closed)
IMPORTANT:
This is set to DRAFT
because there is a discussion of potentially suspending some of the groups and projects consolidation. So reviews are welcome, but please do not merge just yet. Thank you.
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.