https://docs.djangoproject.com/en/4.1/topics/db/queries/#using-custom-
reverse-manager
In the given example, this works well as-is, but if you prefetch_related
the entries when you're querying Blog, Django will use the
prefetch_related cache and ignore the custom manager.
This behavior may/may not be desired, but the documentation could use a
side tip about this condition, maybe in a 'Good to know' infobox.
Also, separately: one flaw in the documented approach is that you have to
explicitly use the custom manager when making a query - there doesn't seem
to be a way to make the custom manager the default, which can cause issues
if you forget to add it to all your calls.
--
Ticket URL: <https://code.djangoproject.com/ticket/34249>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => closed
* resolution: => duplicate
* easy: 1 => 0
Comment:
Duplicate of #30355.
--
Ticket URL: <https://code.djangoproject.com/ticket/34249#comment:1>