#36665: Rewrite reference to model manager usage to avoid saying "tricky"
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Type:
| Cleanup/optimization
Status: new | Component: Database
| layer (models, ORM)
Version: dev | Severity: Normal
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
In the
[https://docs.djangoproject.com/en/5.2/topics/db/optimization/#:~:text=tricky%20so%20don%E2%80%99t%20make%20assumptions.
database optimization doc], there is this advice:
> Understand select_related() and prefetch_related() thoroughly, and use
them:
> - in managers and default managers where appropriate. Be aware when your
manager is and is not used; sometimes this is tricky so don’t make
assumptions.
Saying something is "tricky" and immediately moving on leaves the
impression of information hiding. Let's at least link to something that
explains what to watch out for or debug. In other words, we need to answer
the question, "wait, when ''wouldn't'' my model manager be used"?
(The location of this text is moving in #28586.)
--
Ticket URL: <https://code.djangoproject.com/ticket/36665>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199e3d361a1-d7d9f9d5-68e8-4ac7-b226-615ce529e733-000000%40eu-central-1.amazonses.com.
