Opened 13 years ago
Closed 13 years ago
#17286 closed Bug (fixed)
All cache backends need to call its 'close' function
Reported by: | Owned by: | Grzegorz Nosek | |
---|---|---|---|
Component: | Core (Cache system) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Zbigniew Siciarz | Triage Stage: | Ready for checkin |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Django currently supports multiple cache backends. However, the only DEFAULT_CACHE will be closed when request is finished, just like before as the single CACHE_BACKEND setting.
Should we apply this logic to all the cache backends? Because several memcache backends are totally possible. Think in this user case: one for dramatic data -> shorter timeout, allow evictions; the other for static data -> longer timeout, do not allow evictions.
Please let me know your thought, thanks!
Attachments (1)
Change History (6)
comment:1 by , 13 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 13 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
by , 13 years ago
Attachment: | 17286.diff added |
---|
comment:3 by , 13 years ago
Has patch: | set |
---|
Note:
See TracTickets
for help on using tickets.
Like all database connections are closed at the end of each request, all cache connections should be closed.