Details
Assignee
UnassignedUnassignedReporter
Asher Densmore-LynnAsher Densmore-LynnNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Priority
New
Details
Details
Assignee
Unassigned
UnassignedReporter
Asher Densmore-Lynn
Asher Densmore-LynnNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Priority
Created 13 October 2022 at 16:46
Updated 13 October 2022 at 16:50
I ran into a situation where I knew that the query cache was stale but the tools to peel that query out of the cache are deficient and largely undocumented. A “cachebusting” strategy is deficient because cachebusters get around a cache as long as they’re applied going forward – as soon as the original query is run a second time, the stale data will come right back out of the cache.
Ideally I’d like to be able to pass a boolean to cfquery to tell it that this query should be run and overwrite the cached results.
<CFQUERY name="getData" cacheoverride="#FORM.update ?: false#" cachedwithin="#createtimespan(0,0,10,0)#"> SELECT * FROM myTables T WHERE T.UserID = <CFQUERYPARAM value="#URL.UserID#"> </CFQUERY>