Is there a good way to clear the cache for a specific query instead of the entire query cache (using cachedWithin to put it in the cache)? We see this post about a “tags” argument/attribute but there is no documentation on how to use it with queryExecute and the tags aren’t mentioned anywhere in the docs. Any help on clearing the cache of a specific query would be much appreciated. Thoughts?

just run it again with a 0 cachedwithin value

The problem is we are setting the query into the cache but want to programmatically bust the cache on that query after doing an insert somewhere else in the app. So we were hoping to find a way to bust the cache by an ID or tag or something, but can’t figure out how to target that specific query from another place in the app. Does that make sense?

It's been a long time since I've cached a query on the application side. But, when I did, i would just run the query again after the update/insert/delete (same name) but with a cachedwithin of 0. That clears it. Lucee has a bunch of caching read/clear so I suppose the ability to clear a single query out of the cache could be buried in there somewhere.

Yeah, we’ve been banging our heads on the wall about it. The funny thing is, the options struct of queryExecute says “Struct containing query options, all cfquery tag attributes are supported except the name attribute.” So trying to pinpoint the same query somewhere else has been tough.

Looking that way 😕

@danmurphy Play around with the

getCacheHandlerCollection

object above. I do recall seeing methods that would clear the entire cache (I think the method was

reset()

), but there was just nothing that let me view all the queries in cache.

@zackster can you confirm this? You commented on the ticket https://luceeserver.atlassian.net/browse/LDEV-1280 that says we should be able to set

tags

for the query going into the cache (even within query Execute) and then easily clear it using that same

tags

. What you say in your comment in that ticket seems to be exactly what we’re after, but it just doesn’t seem to work.

do you have a query cache defined? I dug up the commits and the test case, see the ticket

Yes.

yep

use QueryNew and QoQ ?

Oh man, I think I got it. It was hiding in the documentation all along… https://docs.lucee.org/reference/functions/cacheclear.html

2. an Array containing tags defined when put the element to the cache

cool

So there wasn’t a way to say filter=‘myfilter stuff’ or tags=‘myTag stuff’. I guess if it is an array, it just assumes you are targeting tags for the first argument?

thanks @danmurphy for this great post. I could use this too.

Yeah, @danmurphy I'd upvote +10 this post. Going to copy the entire thread and add it to my cheat sheet stuff

anyone feeling like writing a post on dev.lucee.org about this?

Hmm, I can give it a shot. I’ve not been around there much. Just add a new topic you’re saying? Would this be in the documentation or dev category? (Or tell me if I’m in the wrong place entirely).

Are you on twitter? Also we can link this from the caching category on Lucee docs too

@zackster I’m really not. Feel free to tweet away.

only to HT you 🙂

I mean, my handle is

@murphmandan

, but I have about 3 followers probably 😄 .

done https://twitter.com/zackster/status/1489667890722844686