Hello and thanks for the respond.
My knowledge on caching was little. I used it, but I never programmed it
my self. So I had no idea about how the keys would be stored.
The solution was... I did not mess with my memcached.py or anything
else. I just use it as everybody else is using it.
The prob
On Sun, Nov 13, 2011 at 11:35 AM, Cal Leeming [Simplicity Media Ltd]
wrote:
> +1 on hashing the key.
> Just my two cents worth but, the way our company does it as standard is
> something like this:
> import hashlib
> def generate_key(*args, **kwargs):
> return hashlib.sha224(pickle.dumps([args
+1 on hashing the key.
Just my two cents worth but, the way our company does it as standard is
something like this:
import hashlib
def generate_key(*args, **kwargs):
return hashlib.sha224(pickle.dumps([args, kwargs])).hexdigest()
Then you can do stuff like:
lol = YourModel.objects.all()[0]
g
Hi inonc,
>Why am I the only one who seems to be faced with such issues?
>I thought millions out there do use memcached as their backend...?
>Wouldn't be MD5 a great solution to all of us? The guys with small
>sites, don't have issues with scaling, and the guys with big sites are
>in the need of a
4 matches
Mail list logo
