> best method for doing that be to execute the same query and
> give it a new cachedwithin value of #CreateTimeSpan(0,0,0,0)#
> to kill the cache from the backend and then when the frontend
> query is called again, it will reset the cache?
Yes, that works perfectly fine. In fact, if you want to avoid having the
"frontend" user wait for the database, you can flush the query as you
described above, then rerun it with the appropriate cache time again in your
"backend" page.
> I'm just curious how CF differentiates cached queries. If the
> front end has one application name and the backend has another,
> does it handle the cached queries separate even though they're
> the exact same query?
CF compares the exact SQL statement sent to the database, and compares all
of the attribute values for CFQUERY except for CACHEDWITHIN/CACHEDAFTER. If
anything is different, CF will run the query against the database rather
than use the previously cached recordset.
In some versions of CF, the "exact SQL statement" even includes whitespace,
such as tabs, within the CFQUERY block.
CF doesn't use the application name, just the attributes described above.
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]
