#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 mtredinnick):
All the latest reasons I've seen to include this are because "it's a
compromise because of <some bigger problem>". So fix the real issue,
rather than trying to put in a compromise. Sure, it's harder. But it's
much more worthwhile in the long run and helps us work out whether it
really is a bigger problem, or not really a problem and what the possible
alternatives are.
For example, maybe an identity manager, a la #17 (or, at least some
variation on #17, since that ticket wanders all over the place) is the
solution. Maybe the sort of thing we want to do for Django 1.2 or 1.3
allowing specifying an alternative default `QuerySet` class is the right
solution. Maybe it's something else.
Right now, though, I'm unconvinced that we're forced to compromise yet.
--
Ticket URL: <http://code.djangoproject.com/ticket/7338#comment:18>
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 [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
-~----------~----~----~----~------~----~------~--~---
