Ya cache invalidation is something you'll always have a problem with. The clean() method can be used (at the end of a queryset, or on the Manager itself) to force the invalidation.
As for _get_sql_clause I guess I could make it just pull from filters/ extra args to build the key -- not as clean but it's the only other way I can think of. On Jul 4, 11:25 pm, "Jeremy Dunck" <[EMAIL PROTECTED]> wrote: > On 7/5/07, David Cramer <[EMAIL PROTECTED]> wrote: > > >http://www.davidcramer.net/code/50/django-cachemanager.html > > > Criticism welcomed! > > I think the order of bits returned from _get_sql_clause is dependent > on how the queryset is built up, so that you'll cache equivalent > result sets repeatedly. > > And there's the issue of cache invalidation. > > But definitely useful. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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-developers?hl=en -~----------~----~----~----~------~----~------~--~---
