Sometimes it may occur that a user creates a Service Event, associates it with a Service Area, and then later "deletes" the Service Event. Now, if you try to delete that same Service Area in the admin, you're unable too since the SE is only soft deleted.
Obviously we can delete manually via the Django shell, but that's not practical for most people. A couple options off the top of my head:
- Change the Service Area/Unit Service Area/Service Event ForeignKey on_delete chain to CASCADE instead of protect. This could be dangerous though.
- Add ServiceEvent's to the admin so that Service Events can be hard deleted.
- Add a page in the front facing UI to list all soft deleted SE's and allow users to hard delete them from there.
- ... something else?
@ryanbottema what do you think the best way of dealing with this is?