Fix project mirror data schema
What does this MR do?
Adds NOT NULL constraint to the ProjectMirrorData project_id foreign_key and adds uniqueness constraint to the project_id index as well.
Why was this MR needed?
This was causing the db/schema to be both inconsistent between the EE and CE versions of GitLab and between MySQL and Postgres versions.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Review
-
Has been reviewed by UX -
Has been reviewed by Frontend -
Has been reviewed by Backend -
Has been reviewed by Database
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together -
Internationalization required/considered -
End-to-end tests pass ( package-and-qamanual pipeline job)
What are the relevant issue numbers?
Edited by Yorick Peterse