I'm memory constrained and therefore memcache is not an option. The
pages makes a lot of independent SQL queries that is better handled
through one sql call via the db cache backend.
I suppose I could roll my own, but find it odd that somebody hasn't
fixed it. I would fix it myself, if I knew what
May I ask why you are using a database cache, rather than something like
memcache??
Cal
On Tue, Jul 12, 2011 at 5:09 PM, gamingdroid wrote:
> I ran into this problem using django core's database cache:
>
> ERROR: duplicate key value violates unique constraint "cache_pkey"
> STATEMENT: INSERT
And memcached isn't hard to setup at all!
Cheers,
André
On Tue, Jul 12, 2011 at 10:29 PM, Issac Kelly wrote:
> I would guess your quickest way forward is to change backends, as it
> appears that this is a larger issue with database transactions between
> threads, which is a couple of years old.
I would guess your quickest way forward is to change backends, as it
appears that this is a larger issue with database transactions between
threads, which is a couple of years old.
I've been tinkering with LocalMemCache for a really small site, and
django-redis-cache as a toy, I know that some hav
I ran into this problem using django core's database cache:
ERROR: duplicate key value violates unique constraint "cache_pkey"
STATEMENT: INSERT INTO "cache" (cache_key, value, expires) VALUES (E':
1:cms-menu_nodes_en-us_1', E'gAJdcQEoY21lbnVzLmJhc2UKTmF2aW
LOG: server process (PID 8453) was te
5 matches
Mail list logo
