#9961: select_related(depth=0) should be a no-op
---------------------------------------------------+------------------------
Reporter: rdaysky | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.0
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Changes (by mtredinnick):
* stage: Design decision needed => Accepted
Comment:
This seems relatively harmless; it won't impact any fast paths. The
reasoning given in the description is unconvincing, since it's easy to
test that functionality already. However, we currently don't have any way
to turn ''off'' `select_related()` behaviour in a queryset and this would
reintroduce that. There are use-cases for that (when you're passed an
arbitrary queryset and only need something at the most local level, so
wish to ensure the smallest query possible is executed).
The patch needs tests however. If we're going to support this, we need to
ensure it doesn't break. Also needs documentation (in
`ref/models/querysets.txt`).
--
Ticket URL: <http://code.djangoproject.com/ticket/9961#comment:2>
Django <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
