#20945: Allow cache tag to use specified cache config.
---------------------------------+------------------------------------
Reporter: FunkyBob | Owner: nobody
Type: New feature | Status: new
Component: Template system | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by FunkyBob):
Well, yes, and no... I was basing it off the fact staticfiles, by default,
will try to use a different cache backend and fall-back to default. I
think this is a good pattern for more of Django to follow, allowing people
to differentiate if they want.
In our current project we'd like to move all the template fragment caching
to a specific backend.
Perhaps a middle ground solution, and have it look for a fixed name [as
staticfiles does -- I got confused and thought it had a setting] such as
"fragments", and fall back to default otherwise?
--
Ticket URL: <https://code.djangoproject.com/ticket/20945#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.f3441170ef00a5f411275f83fd27aa9a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
