Opened 17 years ago

Last modified 3 weeks ago

#11379 new New feature

MAX_ENTRIES of cache backend should not be required

Reported by: wsorenson Owned by: nobody
Component: Core (Cache system) Version: dev
Severity: Normal 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 (3)

comment:1 by Alex Gaynor, 17 years ago

Triage Stage: Unreviewed → Accepted

comment:2 by josh, 16 years ago

Resolution: → duplicate
Status: new → closed

This is a duplicate of issue #11260

comment:3 by Sarah Boyce, 3 weeks ago

Resolution: duplicate
Severity: → Normal
Status: closed → new
Summary: max_entries should not be required → MAX_ENTRIES of cache backend should not be required
Type: → New feature

#37112 was a duplicate

#11260 suggested doing this to solve a different issue (this issue was wontfixed)

Note: See TracTickets for help on using tickets.
Back to Top