#5: Add a cache=NUM_SECONDS argument to QuerySet
------------------------+---------------------------------------------------
Reporter: adrian | Owner: adrian
Status: reopened | Component: Metasystem
Version: | Resolution:
Keywords: | Stage: Design decision needed
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------+---------------------------------------------------
Comment (by anonymous):
Thanks for the pointer, ubernostrum. That cache documentation describes
exactly what I was suggesting in my first example.
Given that Django has fairly complete caching middleware already
available, I'd recommend that this either be a shortcut (something like my
`get_cached` example above) or just be skipped. The convenience of
embedding caching into the database layer is (IMHO) outweighed by the
unnecessary coupling.
If an application wants to use the admin interface but still support model
caching, invalidation could simply be put in the model's `save` method,
right?
--
Ticket URL: <http://code.djangoproject.com/ticket/5#comment:7>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
