#7338: Method .cache(timeout) in QuerySet
---------------------------------------------------+------------------------
Reporter: marinho | Owner: marinho
Status: assigned | Milestone:
Component: Database layer (models, ORM) | Version: SVN
Resolution: | Keywords:
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------------+------------------------
Comment (by marinho):
Malcolm, I see your point of view.
Maybe there is a better way to make a cache for ORM objects, and since I
started to use Django, I'm thankful to core developers because in 95% of
times you made amazing good choices, and this is why Django is amazing as
it is :)
But I agree to msaelices. I'd like to have a default and strong way to
cache query results, and share this among all users online, and I didn't
see until now a better solution using third part or Manager inheritance,
because there are some times when Django ORM ignores _default_manager and
use its own Memory class. Then, a default cache way would resolve this.
And I like msaelices's idea for invalidation.
But since is a design decision, I have just followed your thoughts and
waited for your decisions :)
--
Ticket URL: <http://code.djangoproject.com/ticket/7338#comment:16>
Django <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 django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
