Sorry - not much time but... If the updates and deletes are simplistic (and rare as you say) you _might_ want to not redo the whole main query, but rather update it as well.
Remember that you can modify any query in memory using all the variable manipulation tools at your disposal. That way you get the updated data in your query but don't incur the refresh time (or at least as much of it). The main query will still be rerun on it's scheduled out-of-cache time. So periodically you'd get the "real thing". Jim Davis > -----Original Message----- > From: James Blaha [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 15, 2003 10:10 AM > To: CF-Talk > Subject: I need some good old advice. > > All: > > I need some good old advice. I'm redesigning an application to utilize > query caching and the use of Query of Query to speed it up some. So I'm > caching one large query and running the application templates using Q0Q. > Any time there that there is an insert, update or deletion from the > database I'm going to un cache the main query. The QoQ's will always > have correct data as changes happen which shouldn't be all that often. > > My question is when I perform a SQL insert, update or delete is there a > way to call and run a query but not have that query add to the execution > time of the template. For example maybe and idea is calling a scheduled > job to run the query. > > Regards, > James Blaha > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
