> > CACHEDWITHIN set to a timespan of zero, that'll remove
> > the previous cached query from the cache. Someone will
> > need to rerun the query against the database to recache
> > it, though.
>
> That was my point (however unclear it may have been!), if I'm
> reading your post correctly. When you change the cachedwithin
> value to 0, the query does not refresh itself on that
> specific call (because you've just changed the value and the
> query is still cached). It doesn't get run and re-cached
> until the *next* page request (which is usually when that
> query is called again, unless you run a cfhttp request to
> programatically call that page again or something similar).
>
> Or did I misunderstand?
I'm sorry, I must have misunderstood you. Changing the CACHEDWITHIN value to
zero causes the previous recordset to be overwritten with a new one fetched
from the database, which is itself immediately discarded since it has a
cache time of zero. The net result is that the query is no longer cached.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
