#25279: Make prefetch_related_objects a public API
-------------------------------------+-------------------------------------
Reporter: adamchainz | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Seems related to #24975 which proposes to add the ability to call
`prefetch_related()` on a model instance. I wonder if we could find a
common solution to address both of these tickets.
If we make `prefetch_related_objects()` public, I think some tests would
also be needed to ensure that it isn't refactored so that it's signature
changes.
--
Ticket URL: <https://code.djangoproject.com/ticket/25279#comment:1>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.aac31eaaaaa0c930c5f088ff77a18e00%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.