#23266 closed Bug (fixed)
Query relation lookup check issues extra queries.
| Reported by: | Florian Apolloner | Owned by: | Anubhav Joshi |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | dev |
| Severity: | Release blocker | Keywords: | |
| Cc: | Tim Graham, ANUBHAV JOSHI | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The fix for #14334 issues extra queries when doing relational lookups with __in and a qs as argument. https://github.com/django/django/commit/34ba8670#diff-0edd853580d56db07e4020728d59e193R1100 should check if value is a qs and then check the modeltype or whatever. This release blocker is only for 1.8
Change History (3)
comment:1 by , 11 years ago
| Component: | Uncategorized → Database layer (models, ORM) |
|---|---|
| Has patch: | set |
| Owner: | changed from to |
| Status: | new → assigned |
| Triage Stage: | Unreviewed → Accepted |
comment:2 by , 11 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
https://github.com/django/django/pull/3039