cached_db session with memcached forgets big values
Considering memcached's 1MB limit, putting a value larger than 1MB into a cached_db session will get written to DB but not to cache. However a previous value for the session key already exists in the cache, and thus the session gets restored with previous data from the cache, instead of the new information stored in django_session table, in the DB.
My guess is that the memcached backed should remove the key when not being able to set it to the new value.
Attachments
(1)
- memcached.py.patch
(640 bytes
) - added by ccrisan 13 years ago.
- patch for memcached.py that makes the backend clear a key if unable to set it
Download all attachments as:
.zip
Change History
(10)
Owner: |
changed from nobody to anonymous
|
Status: |
new → assigned
|
Triage Stage: |
Unreviewed → Accepted
|
Needs tests: |
set
|
Patch needs improvement: |
set
|
Version: |
1.3 → SVN
|
Needs tests: |
unset
|
Owner: |
changed from anonymous to Michael Manfre
|
Patch needs improvement: |
unset
|
Triage Stage: |
Accepted → Ready for checkin
|
Resolution: |
→ fixed
|
Status: |
assigned → closed
|
patch for memcached.py that makes the backend clear a key if unable to set it