Opened 15 years ago
Closed 14 years ago
#13066 closed (duplicate)
cache.get and cache.set should have consistent key rules across different backends
Reported by: | rbanffy | Owned by: | nobody |
---|---|---|---|
Component: | Core (Cache system) | Version: | dev |
Severity: | Keywords: | ||
Cc: | Triage Stage: | Design decision needed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
As it is now, cache.get and cache.set accept keys with spaces when CACHE_BACKEND is set to 'locmem://', but memcached complains of keys with spaces. This makes tests work on a non-memcached setup (i.e. development workstation) and fail on the server (using memcached)
Change History (4)
comment:1 by , 15 years ago
Triage Stage: | Unreviewed → Accepted |
---|---|
Version: | 1.2-beta → SVN |
comment:2 by , 15 years ago
milestone: | 1.2 |
---|---|
Triage Stage: | Accepted → Design decision needed |
comment:3 by , 15 years ago
Fair enough re 1.2 milestone.
This is actually probably a duplicate of #6447, though this ticket more clearly requests what I think is the right solution; that the caching system should enforce the most-stringent key rules of any cache backend so code with bad keys fails fast rather than in production only. Seems like this is the unavoidable solution if cache backends are really intended to be interchangeable, and for caching to be usable by reusable code. AFAICS that solution was never proposed or rejected in any of the previous related tickets.
comment:4 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Marking duplicate of #6447.
I've also been bitten by this.