#15149: Memcached backend: possible issue with cache keys
----------------------------------------------+-----------------------------
Reporter: jeff@… | Owner: nobody
Status: new | Milestone:
Component: Cache system | Version: SVN
Resolution: | Keywords: memcached
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 |
----------------------------------------------+-----------------------------
Comment (by russellm):
The fact that the set debug isn't being printed is *very* suspect. When
combined with the fact that the set() calls are evidently calling the
caching functions without any prefixes, it suggests that some old caching
code is being invoked for some reason.
Could you try purging all the .pyc files from your django directory, and
rerun the tests. I have no idea how you'd be getting half an updated class
(updated gets, but not sets), but it's worth a try.
Failing that - Do you get the same results if:
* You use get_cache() directly, instead of the default cache object.
i.e.:
{{{
from django.core.cache import get_cache
mycache = get_cache('default')
mycache.get('testing_yo')
...
}}}
* You use a manually instantiated cache object:
{{{
from django.core.cache.backends.memcached.MemcachedCache
mycache = MemcachedCache('127.0.0.1:11211', KEY_PREFIX='lendle_')
mycache.get('testing_yo')
...
}}}
--
Ticket URL: <http://code.djangoproject.com/ticket/15149#comment:10>
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.
