It might depend on your cache setting in setting.py, and the devserver reloading on file change. I've had that happen and confuse things a bit. Going straight to memcache or file based for low level caching development was the only way to get consistent.
There are also some limitations on the size of objects that can be stored depending on the cache backend. I'm using the cache for searches by caching just a list of the ids and then doing db queries for the subset I need on each page like X.objects.filter(pk_in=cachedids[10:20]). I also prefix the session key to the cache key, so different users aren't sharing the same cached object (for things like search caching anyway). Thats not using the built-in pagination though, so you might have to build your own doing it just with ids. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
