Context Navigation

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

v1	v2
1	1	Thank you both for your answers ! If I may give a bit more context. I understand this is only for single instances, but end users are always happy if CRUD endpoints are faster (especially if called multiple times, with multiple nested objects).
2	2
3		- Using `foo.bar_set.all()` will not necessarily fill up nested objects (and `to_attr`), and each level will trigger lazy queries.
	3	- Using `foo.bar_set.all()` will not necessarily fill up nested objects (and `to_attr`), and each level will trigger lazy queries (potentially N+1 queries).
4	4	- My instance has initially been created with both `select_related` and `prefetch_related` via a queryset in a drf view. From a user point of view, I can do like below but the API feels a bit inconsistent. Especially users would not expect the current silent behavior if they try to set a prefetch in the `from_queryset` and see that it is not working.
5	5	{{{