Opened 5 years ago

Closed 4 years ago

#11379 closed (duplicate)

max_entries should not be required

Reported by: wsorenson Owned by: nobody
Component: Core (Cache system) Version: master
Severity: Keywords: max_entries cache
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


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.

Attachments (0)

Change History (2)

comment:1 Changed 5 years ago by Alex

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

comment:2 Changed 4 years ago by josh

  • Resolution set to duplicate
  • Status changed from new to closed

This is a duplicate of issue #11260

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.