You don't need to change the name of the query. If the SQL is different then CF knows it's a different query.
> -----Original Message----- > From: Dave Watts [mailto:[EMAIL PROTECTED] > Sent: Thursday, 3 July 2003 11:24 a.m. > To: CF-Talk > Subject: RE: Caching query theory > > > 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 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
