Opened 16 years ago
Closed 14 years ago
#11269 closed (fixed)
Allow key_prefix to be callable
Reported by: | Mikhail Korobov | Owned by: | nobody |
---|---|---|---|
Component: | Core (Cache system) | Version: | dev |
Severity: | Keywords: | ||
Cc: | miracle2k, Zeth | Triage Stage: | Accepted |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
"cache_page" decorator accepts "key_prefix" argument.
If "cache_page" will allow "key_prefix" to be callable it will be easier to fine-tune view caching.
For example, it will be easier to have per-user cache or to cache views based on specified GET parameters (there is dedicated #4992 ticket for that).
I've attached patch for that feature.
The sample syntax:
#have 2 static versions of the my_view response for authenticated and anonymous users def my_key_prefix(request): if request.GET: return None #magic value to disable caching if request.user.is_authenticated(): return 'logged_in' else: return 'not_logged_in' @cache_control(must_revalidate=True) @cache_page(600, my_key_prefix) def my_view(request): ....... #something is different for authenticated and anonymous users
#cache my_paginated_view based on "page" parameter in query string def page_key_prefix(request): return request.GET.get('page','') @cache_page(60, page_key_prefix) def my_paginated_view(request) .... #page number is passed via 'page' GET parameter and used for pagination
Attachments (1)
Change History (9)
by , 16 years ago
Attachment: | callable_key_prefix.diff added |
---|
comment:1 by , 15 years ago
comment:2 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:3 by , 15 years ago
Cc: | added |
---|
comment:4 by , 15 years ago
For the second example, that of get parameters, I just generalise the whole thing, i.e. any and all get parameters are used for the key_prefix.
i.e. something like:
def get_requests(request): """Turn the GET parameters into a string. Used for caching.""" key_prefix = "" # Get the parameters out parameters = request.GET.items() # Sort them so we only have one order in the cache parameters.sort() # Turn it into a string for pair in parameters: for item in pair: key_prefix += "%s-" % item return key_prefix @cache_page(600, my_key_prefix) def my_view(request): #blah blah
This pattern seems to work for all the situations I have encountered so far. This seems to be more DRY than the example above.
comment:5 by , 15 years ago
Cc: | added |
---|
comment:6 by , 15 years ago
zeth, your get_requests doesn't provide support for multiple GET-variables with the same name (for example, checkboxes sent via GET), so cached results for /?a=1 and /?a=1&a=3 would be the same.
comment:7 by , 15 years ago
The workaround is to use
parameters = dict(request.GET).items()
instead of
parameters = request.GET.items()
comment:8 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
#13795 should have taken care of any use case for this.
Standalone app with cache_page_with prefix decorator:
http://bitbucket.org/kmike/django-view-cache-utils/