Opened 16 years ago
Closed 15 years ago
#11379 closed (duplicate)
max_entries should not be required
| Reported by: | wsorenson | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | dev |
| Severity: | Keywords: | max_entries cache | |
| Cc: | Triage Stage: | Accepted | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Not every Django project's cache will want to use a max_entries (this could also apply to timeout).
There should be a simple way to turn off this parameter, such as max_entries=0 / timeout=0.
Change History (2)
comment:1 by , 16 years ago
| Triage Stage: | Unreviewed → Accepted |
|---|
comment:2 by , 15 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
This is a duplicate of issue #11260