Given that this issue has been open for some time, we should update the documentation which is giving incorrect information to developers.
I have added an example of how best to manage cascade_deletes between many_many related objects.
To avoid adding confusion, I decided against adding the alternative solution using onBeforeDelete() and removeAll(). However this can also be added if you think it is needed, or better?
[x] All commits are relevant to the purpose of the PR (e.g. no TODO comments, unrelated rewording/restructuring, or arbitrary changes)
Small amounts of additional changes are usually okay, but if it makes it hard to concentrate on the relevant changes, ask for the unrelated changes to be reverted, and submitted as a separate PR.
Description
Given that this issue has been open for some time, we should update the documentation which is giving incorrect information to developers.
I have added an example of how best to manage
cascade_deletes
betweenmany_many
related objects.To avoid adding confusion, I decided against adding the alternative solution using
onBeforeDelete()
andremoveAll()
. However this can also be added if you think it is needed, or better?Issues
Pull request checklist