tracker issue : CF-4087462

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

[ANeff] Bug for: QueryExecute() ignores CachedWithin

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

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

Created: 11/15/2015

Components: Caching

Versions: 11.0

Failure Type:

Found In Build/Fixed In Build: CF11_Final /

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Windows 10 64 bit

Vote Count: 2

Listed in the version 2016.0.0.297996 Issues Fixed doc
Verification notes: verified_fixed on July 26, 2017 using build 2016.0.01.298513
QueryExecute() ignores CachedWithin regardless if "Use internal cache to store queries" is enabled or not.

Repro:

1) Run this

<cfscript>
  q = queryExecute("SELECT artName FROM art WHERE artID = 1", [], {datasource="cfartgallery", cachedwithin=createTimeSpan(0,0,0,15)});
  writeOutput(q.artName);
  queryExecute("UPDATE art SET artName = 'charles1_temp' WHERE artID = 1", [], {datasource="cfartgallery"});
  q = queryExecute("SELECT artName FROM art WHERE artID = 1", [], {datasource="cfartgallery", cachedwithin=createTimeSpan(0,0,0,15)});
  writeOutput(q.artName);
</cfscript>

Expected output: charles1charles1

Actual output: charles1charles1_temp

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

Watson Bug ID:	4087462

External Customer Info:
External Company:  
External Customer Name: Aaron Neff
External Customer Email:  
External Test Config: Verified in CF11 Update 5 (build 11,0,05,293506). The issue does not exist in build 11,0,0,296013. But the issue should be fixed in CF11 as query caching is a commonly used feature and should be reliable w/o requiring version upgrade.

Attachments:

Comments:

+1 ..... Have noticed similar behavior.
Vote by External U.
5343 | November 15, 2015 10:09:07 PM GMT
+1 Will be moving to CF11 soon and will need to be able to cache queries using queryExecute().
Vote by External U.
5344 | November 16, 2015 09:45:46 AM GMT
Will this be fixed in a future update for CF11?
Comment by External U.
5339 | March 02, 2016 07:21:50 PM GMT
Hi Adobe, +1 to Carl's question. Are you only fixing this in CF2016? It should also be fixed in -CF11-. So, to repeat Carl's question, will this be fixed in CF11? You know it'd streamline communication if you populate the "Fixed In Build" field. Thanks!, -Aaron
Comment by External U.
5340 | April 01, 2016 01:03:58 PM GMT
This issue is fixed and it will be available as part of an upcoming update of ColdFusion 11.
Comment by Nimit S.
5341 | April 02, 2016 10:27:27 PM GMT
Verified this is fixed in CF2106 Update 1 (build 2016.0.01.298513). This should be listed on https://helpx.adobe.com/content/dam/help/attachments/cf2016-issues-fixed.pdf, since CF11's fix came after CF2016 was released. Thanks!, -Aaron
Comment by Aaron N.
5342 | July 26, 2017 08:09:15 AM GMT