#26172: Don't query the database when filtering an already empty queryset
-------------------------------------+-------------------------------------
Reporter: seddonym | Owner: nobody
Type: | Status: closed
Cleanup/optimization |
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: orm, queryset | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by akaariai):
The main reason why we use the caching approach we currently use is that
we have done it in this way always.
If we started from scratch, it might be we would opt for an explicit
approach - queries are only executed when qs.execute() is called. That way
the user would know exactly when the cache is created and cleared. But we
are extremely unlikely to change any of this now...
--
Ticket URL: <https://code.djangoproject.com/ticket/26172#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.078c2bc373daee22e9d1cd67177ab303%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
