#26128: Colon separate JOIN TYPE in QuerySets.select_related() and
QuerySets.prefetch_related()
-------------------------------------+-------------------------------------
Reporter: vinaykrsharma | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: custom join | 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):
* status: new => closed
* needs_better_patch: => 0
* resolution: => needsinfo
* needs_tests: => 0
* needs_docs: => 0
Comment:
I don't think that particular API is likely to be accepted. Maybe custom
`SelectRelated` classes as described in #23854 would allow allow your use
case? Did you check if the custom `Prefech` object would work for what
you're trying to accomplish there. It's helpful to explain what your use
case actually is instead of just proposing some functionality. Another
related ticket might be #25590, "Allow fields to set join class". Please
have a look through the other "Database layers" tickets and add more
details here if you don't any of them will address what you're trying to
accomplish. Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/26128#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/071.cafafb4746dbe14f170c62c2cc4b7744%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
