> We have a monster app...we are caching queries here and > there...so when it sees a query that is cached, it checks > to see if its different to know if to use the old one > when they have the same name, correct?
Yes, CF compares the CFQUERY tag attributes (with the exception of the CACHEDWITHIN/CACHEDAFTER attributes) and content, and if they're all the same, it'll use the cached query. > Soooo, following that, if in the customer management > section of the system there is a nasty little query, > which then usually gets used later in the ordering > process, would using query_name_customerID and caching > for 10 minutes be the appropriate way to handle this? I don't know if it's the best way, but it should work. If the query is specific to a single customer, you could just as easily store it in the Session scope. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ voice: (202) 797-5496 fax: (202) 797-5444 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
