#8410 closed (fixed)
memcache backend add method is inconsistent with it's other methods
| Reported by: | trbs | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Cache system) | Version: | dev |
| Severity: | Keywords: | memcached, consistency, add | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The add method of the memcached backend uses a different approach for it's key/value pair then the other methods.
Seems to be 'left' over from past changes/fixes ?
Patch attached here aims to make 'add' consistent in terms of handling the key/value pair as it's brother the 'set' method.
Attachments (1)
Change History (4)
by , 16 years ago
| Attachment: | patch-django.core.backends.memcached-8410.diff added |
|---|
comment:1 by , 16 years ago
| milestone: | → 1.0 |
|---|---|
| Triage Stage: | Unreviewed → Ready for checkin |
comment:2 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [8444]) Fixed #8410 -- Added a missing piece of value encoding for the memcached
backend. Patch from trbs.