[Django] #16856: Add a way to clear select_related
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
Milestone: | Component: Database
Version: SVN | layer (models, ORM)
Keywords: | Severity: Normal
Has patch: 0 | Triage Stage:
Needs tests: 0 | Unreviewed
Easy pickings: 0 | Needs documentation: 0
| Patch needs improvement: 0
| UI/UX: 0
-------------------------------------+-------------------------------------
If you've got a queryset that has had select_related called on it (maybe
passed to you from some other code you don't control) there's currently no
documented way to clear out select_related.
One possible API is .select_related(None), which mirrors how .defer()
works.
The combination of this and #16855 would make .select_related() and
.defer() more consistent with each other, which would be nice.
--
Ticket URL: <https://code.djangoproject.com/ticket/16856>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
feature | Component: Database layer
Milestone: | (models, ORM)
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* stage: Unreviewed => Accepted
Comment:
There was a clear consensus on this API in #django-dev.
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:1>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
feature | Component: Database layer
Milestone: | (models, ORM)
Version: SVN | Severity: Normal
Resolution: | Keywords:
Triage Stage: Accepted | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
* cc: jdunck@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:2>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by seldon):
* cc: seldon (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:3>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* cc: botondus@… (added)
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:4>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by bberes):
For anyone reading this, the undocumented hacky way to do this is:
`qs.query.select_related = False`
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:5>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by dcramer):
Patch is here
https://github.com/django/django/pull/665
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:6>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Type: New feature | Status: new
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* cc: timograham@… (added)
* has_patch: 0 => 1
Comment:
Added a release note & brought patch up to date.
https://github.com/django/django/pull/1234
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:7>
Django
-------------------------------------+-------------------------------------
Reporter: carljm | Owner: nobody
Component: Database layer | Version: master
Severity: Normal | Triage Stage: Accepted
Keywords: | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"5074c75a37f88726f3ae057999144545881d3cfc"]:
{{{
#!CommitTicketReference repository=""
revision="5074c75a37f88726f3ae057999144545881d3cfc"
Fixed #16856 - Added a way to clear select_related.
Thanks Carl for the suggestion and David Cramer for the patch.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/16856#comment:8>