Hey Peter, thanks for the reply. You're right, it wasn't really required. The way that I had structured my code previously (without getting into exact details) cached depending on the two criteria "alphaID" and "betaID". Having a second look, I only really had to cache depending on "alphaID" and just had to make sure that I did a cache-clear when "betaID" changes. This also has the added side-effect that I'm not using up more memory than I really need, i.e. for one "alphaID" I should only have a single cached record. Oversight on my part!
On Jun 24, 10:22 am, "Peter J. Farrell" <[email protected]> wrote: > Adrian Scott said the following on 06/24/2009 11:48 AM:> Is there any > possible way of accomplishing this, or should I resort to > > figuring out a different way of structuring my code? > > I don't think it's possible. The criteria is used to generate the cache > key and therefore you need all the data points used to generate the key > to clear a cache element. Ultimately, behind the scenes Mach-II uses > all the data points and hashes them together to create a cache key so > it's not possible to search for keys that begin with a particular string. > > Trying to figure out a situation where this would be required. Could you > share more on the structure of your caching situation? > > .pjf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to Mach-II for CFML list. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/mach-ii-for-coldfusion?hl=en SVN: http://greatbiztoolsllc.svn.cvsdude.com/mach-ii/ Wiki / Documentation / Tickets: http://greatbiztoolsllc.trac.cvsdude.com/mach-ii/ -~----------~----~----~----~------~----~------~--~---
