cfquery cachedafter| View in Tracker
Failure Type: Incorrectly functioning
Found In Build/Fixed In Build: 2016,0,04,302561 / 303574
Priority/Frequency: Normal / Some users will encounter
Locale/System: English / Win 2012 Server x64
Vote Count: 0
Problem Description: cfquery returns cached results even when the cachedafter date is updated to be after the date of the original cached query date, but is still a past date. Steps to Reproduce: See example.cfm to reproduce. Expected Result: * Only the third row should be cached (at least that's how it worked in CF 10.0.22.301868). Query 1 runs before the cachedAfter date so it should not be cached. * Query 2 runs after the cachedAfter date, but it is the first to do so, so it doesn't have previously cached data to return so it should retrieve live data and cache it for any future queries using the same cachedAfter date. * Query 3 also runs after the same cachedAfter date so it should return cached data from Query 2. * Although Query 4 runs after the cachedAfter date, the date has been modified to be after the original cached query date of Query 2, so according to the documentation (and previous CF versions) it should retrieve live data and cache it for future queries using the newly modified cachedAfter date. * Query 5 runs with a cachedAfter date set in the future so it should retrieve live data. Actual Result: The 4th query returns cached data, even though the cachedAfter attribute has been changed to a date that is after the date of the original cached query (row 2). Also, Query 2 is returning cached data except when the page is first requested after cleaning the query cache via the Administrator, but it should never return cached data since it's the first execution that runs after the cachedAfter date, Any Workarounds: None other than to avoid using cachedafter.
- June 01, 2017 00:00:00: example.cfm