Use foreign keys with cascade delete to optimize project removal
requested to merge 1163-deleting-a-project-results-in-a-large-number-of-sql-requests-that-could-be-optimized into master
What does this MR do?
Use foreign keys with cascade delete to optimize project removal
Are there points in the code the reviewer needs to double check?
We should test this in staging and see if the migration runs through without problem, and how long it takes
Why was this MR needed?
Deleting a project results in an absurd amount of queries for big projects
Does this MR meet the acceptance criteria?
-
CHANGELOG entry added -
Documentation created/updated -
API support added - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master(if you do - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Closes #1163 (moved)