RE: Caching query theory

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

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

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

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