No Cascading Delete for Many-to-Many relationships #34
Description
The default behavior for a database is that if you delete a record, the delete will cascade into anything that uses that record as a foreign key (i.e. when you delete a profile, anything records with that profileid as a foreign key will also be deleted). Our current implementation does not support this, meaning if, for example, you were to delete a profile, there would still exist ensemble memberships, plays instrument, and media records associated with a profileid that no longer exists.
This may not be an issue as I don't think we will do much deleting, but the main way this could cause an issue is if an ensemble was trying to display its members it could try to access a profile that no longer exists