Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix: Use a "through" model for the ManyToManyField fields in CourseSe…
…ction and CourseSectionSequence to ensure that cascading deletes will occur to delete the relation upon deletion of a foreign-keyed object. This commit is phase 2 of 3 in order to ensure a smooth deploy. The phases: 1) Add separate through models for user partition groups, add fields to point to the separate models, and start writing to those fields as well. (COMPLETE) 2) After all models have been re-generated, switch code over to use separate through model fields backed by the separate through models *and* stop writing to the original ManyToManyField field. (This PR!) 3) After phase 2 is deployed smoothly, remove the original ManyToManyField fields and rename the new fields to have the same name as the old fields. This PR is designed to be able to easily be rolled-back if anything goes wrong.
- Loading branch information