I agree that this example isn't particularly worrying. It's something an experienced developer wouldn't do. On the other hand, we are aiming at making things simpler for non-experienced developers. To me the worrying part here is that we really don't have any data or experience about if the cure will be worse than the disease. Likely not, but what do we gain by taking risks here? Maybe we should just add the queryset method. This is the smallest atomic task that can be done. Even if there's only the queryset method available, it's possible to enable prefetches per model by using a Manager. - Anssi -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to firstname.lastname@example.org. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/c9d9dca0-f71d-48dd-9985-17ef8b8ec95d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.