#25613 closed New feature (duplicate)
Transactional Cache TestCase
| Reported by: | Hatem Nassrat | Owned by: | nobody |
|---|---|---|---|
| Component: | Testing framework | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
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.
Change History (2)
comment:1 by , 9 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
| Summary: | Trasactional Cache TestCase → Transactional Cache TestCase |
Note:
See TracTickets
for help on using tickets.
As far as I can tell, this is a duplicate of #11505. If not, please describe the issue and proposed solution in a bit more detail. Thanks!