Context Navigation

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

v1	v2
5	5
6	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/
	7
	8	That's not to say you are incorrect, I think there may still be situations such as you describe: I guess there could be cause to use an unmanaged through model with managed models at either end, that was actually a table.