The endpoint was a DRF list view on a fleet-compliance API: drivers, each with a carrier and a most-recent inspection, three serializer levels deep. Django Debug Toolbar showed a few hundred queries for one page of results. Nothing was broken. The select_related() chain in the viewset had simply stopped matching the fields the serializer touched, which is where every serializer older than about a year ends up — the query lives in the view, the field access lives in the serializer, and no part of Django connects the two.
Django 6.1, released on 5 August 2026 , ships a feature aimed squarely at that gap. Fetch modes let you tell a queryset what to do when something later asks for a field the query didn't load. The release announcement leads with it: "Model field fetch modes for configuring on-demand fetching behavior" .…