Context Navigation

Changes between Initial Version and Version 1 of Ticket #26304, comment 4

initial	v1
4	4	> Don't you run into an issue if the rows on either end of the M2M field are truncated but the rows in the through table still exist pointing to nowhere, which effectively would blow up with broken foreignkey constraints?
5	5
6		In my case, it is a View that is acting as the model source: which cannot _ever_ be truncated.
	6	In my case, it is a View that is acting as the model source: which cannot _ever_ be truncated. In this particular instance, it's something very much like http://schinckel.net/2016/01/27/django-trees-via-closure-view/