tracker issue : CF-3846186

select a category, or use search below
(searches all categories and all time range)
Title:

[ANeff] Bug for: cacheRemove()'s exact=false behaves as exact=true if exact ID match found

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Aaron Neff / Aaron Neff (Aaron Neff)

Created: 11/02/2014

Components: Caching

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / Some users will encounter

Locale/System: English / Win All

Vote Count: 0

Listed in the version 11.0.03.292480 Issues Fixed doc 
If an exact ID match is found, cacheRemove()'s exact=false behaves as exact=true.

Repro:

<cfscript>
  cacheRemoveAll();
  cachePut("ab", "");
  cachePut("abc", "");
  cachePut("abcd", "");
  writeDump(cacheGetAllIds());//returns ["ab","abc","abcd"]
  cacheRemove("ab", true, "object", false);
  writeDump(cacheGetAllIds());//returns ["abc","abcd"] (bad - it should return [])
  cacheRemove("a", true, "object", false);
  writeDump(cacheGetAllIds());//returns [] (good)
</cfscript>

Actual result: cacheRemove("ab", true, "object", false) only removes object "ab" from the cache, b/c it was an exact match.

Expected result: cacheRemove("ab", true, "object", false) should remove all 3 objects from the cache, b/c exact=false is supposed to remove all objects whose IDs are _prefixed_ with the specified string.

Verified in 10.0.13.287689 and 11.0.03.291742.

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3846186

External Customer Info:
External Company:  
External Customer Name: itisdesign
External Customer Email:

Attachments:

Comments:

I've verified this is fixed in CF11 Update 3 (11,0,03,292024(PreRelease)). Thanks!, -Aaron
Comment by External U.
10331 | November 08, 2014 05:49:15 PM GMT