Closed (fixed)
Project:
Cache Router
Version:
5.x-1.0-beta4
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
28 Jul 2008 at 21:12 UTC
Updated:
14 Jul 2012 at 23:24 UTC
Jump to comment: Most recent file
The current implementation (D5-branch) of caching using the FILE-engine does not provide a solution for wildcards in cache_clear_all();
Problem:
All $keys are stored as there md5-counterpart:
ex: content:160137:160831
=> stored as fffe5d13a598d9952eafc0bf1b64ba7d
This way we can not find any 'related' keys when cache_clear_all() request the deletion of "content:160137*"
Possible solution:
we should add some more information in the filename
ex: content:160137:160831
=> stored as fffe5d13a598d9952eafc0bf1b64ba7d--content:160137:160831
file_scan_directory() can be used to find all cache-files that fall into the group "content:160137*".
This issue is related to #279152
My patch is in attachment. It adds the current $key to the end of the md5 cache-filename; and it searches for all the files when cache_clear_all() is called with wirldcard=TRUE.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | patch_cacherouter_file_288318.patch | 2.35 KB | Jo Wouters |
Comments
Comment #1
Jo Wouters commentedpatch in attachment.
Note:
Make sure to also apply patch #266532: CACHE_PERMENANT should be CACHE_PERMANENT (this is an issue for D5 too)
Comment #2
slantview commentedThanks Jo. Got this committed to both DRUPAL-5 and DRUPAL-6--1 branches.
Comment #3
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.