Context Navigation

Changes between Version 1 and Version 2 of Ticket #21760, comment 11

v1	v2
1	1	We discussed this issue with @akaariai on IRC.
2	2
3		Like we did for #21410, we'll take a practical approach for fixing the regression from Django 1.6 to master and go for the proposed fix. It's worth noting that the inefficient query will still be present for multicolumn relations, but these are not documented and one needs to use private APIs to make them, so that doesn't qualify as a regression.
	3	Like we did for #21410, we'll take a practical approach for fixing the regression from Django 1.6 to master and go for the proposed fix. It's worth noting that the inefficient query will still be present for multicolumn relations, but these are not documented and one needs to use private APIs to make them, also these have never seen the "joinless" query, so that doesn't qualify as a regression.
4	4
5	5	The implementation of `ReverseSingleRelatedObjectDescriptor.get_prefetch_queryset()` really ought to be cleaned up at some point, especially when we land the patch for composite fields but it'll require a fair amount of refactoring so it only qualifies for master.