RE: Caching query theory
If the 5 phone reps will only be dealing with one customer at a time I don't see why this is a problem, perhaps I haven't understood you correctly. The performance drain in an application is nearly always going to be where you have CF interacting with a third party process, Database, mail server, COM etc. So in this case I would think using the session for a small amount of data would be preferable to hitting the database with huge queries if it can be avoided. Just my 2pence Kola >> -Original Message- >> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >> Sent: 03 July 2003 18:34 >> To: CF-Talk >> Subject: RE: Caching query theory >> >> If it was a customer logged in and running through, yes, then session >> scope >> makes sense, but we have 5 phone reps running this thing, and placing a >> bunch of garbage in and out of session scope just in case of an order >> after >> customer lookup is taxing, right, versus just doing the query? So best >> case >> we have now is just let sleeping dogs lay as is I spose. >> >> Thanks. >> >> >> Regards, >> >> Eric >> >> "The reasonable man adapts himself to the world; the unreasonable one >> persists in trying to adapt the world to himself. Therefore all >> progress depends on the unreasonable man." >> -- George Bernard Shaw >> >> >> -Original Message- >> From: Dave Watts [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, July 02, 2003 6:24 PM >> To: CF-Talk >> >> > 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. >> >> > S, 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 Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
RE: Caching query theory
If it was a customer logged in and running through, yes, then session scope makes sense, but we have 5 phone reps running this thing, and placing a bunch of garbage in and out of session scope just in case of an order after customer lookup is taxing, right, versus just doing the query? So best case we have now is just let sleeping dogs lay as is I spose. Thanks. Regards, Eric "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." -- George Bernard Shaw -Original Message- From: Dave Watts [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 02, 2003 6:24 PM To: CF-Talk > 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. > S, 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
RE: Caching query theory
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. > > > S, 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
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. > S, 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
