#25613: Trasactional Cache TestCase
-----------------------------------+--------------------
Reporter: pykler | Owner: nobody
Type: New feature | Status: new
Component: Testing framework | Version: 1.8
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-----------------------------------+--------------------
TLDR; Having the cache backend refresh much like databases would make life
a lot easier
Caching is truly awful in django and testing custom cache mixins are hard.
The exact problem I am having is a mix of `make_middleware_decorator` +
`FetchFromCacheMiddleware` which i used to create a CacheMixin for
selective caching, to be used alongside UpdateCacheMiddleware (which I
also had to override so it doesn't vary on google analytics cookies and
what not). This is starting to be more about why Caching logged in content
is problematic in django rather than the feature request.
--
Ticket URL: <https://code.djangoproject.com/ticket/25613>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/049.75b5457974d84c455a5fd98593b0a26c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
