#16773: QuerySet.count does no caching until the result cache is filled
-------------------------------------+-------------------------------------
Reporter: | Owner: nobody
eternicode | Status: new
Type: Bug | Component: Database layer
Milestone: | (models, ORM)
Version: 1.3 | Severity: Normal
Resolution: | Keywords:
Triage Stage: | Has patch: 0
Unreviewed | Needs tests: 0
Needs documentation: 0 | Easy pickings: 0
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Changes (by eternicode):
* stage: Design decision needed => Unreviewed
Comment:
tarequeh, good points. I knew there were cases like these that I just
wasn't thinking of.
Seems the create/delete could be solved with post_save and post_delete
signal handlers, respectively, that clear the count cache. That's
probably overkill, though, and maybe even approaching the realm of custom
code for a specific purpose.
--
Ticket URL: <https://code.djangoproject.com/ticket/16773#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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
