So if I understand that correctly if I run this query: <cfquery name="myquery" datasource="#request.dsn#"> SELECT * FROM tblSites WHERE siteID=2 </cfquery>
AND THEN <cfquery name="myquery" datasource="#request.dsn#"> SELECT * FROM tblSites WHERE siteID=1056 </cfquery> It will cache them BOTH and will not return the data from the query WHERE siteID=2 to the user who just rean WHERE siteID=1056 ??? Is that right? Please say yes :) Joshua Miller Head Programmer / IT Manager Garrison Enterprises Inc. www.garrisonenterprises.net [EMAIL PROTECTED] (704) 569-9044 ext. 254 ************************************************************************ ************* Any views expressed in this message are those of the individual sender, except where the sender states them to be the views of Garrison Enterprises Inc. This e-mail is intended only for the individual or entity to which it is addressed and contains information that is private and confidential. If you are not the intended recipient you are hereby notified that any dissemination, distribution or copying is strictly prohibited. If you have received this e-mail in error please delete it immediately and advise us by return e-mail to [EMAIL PROTECTED] ************************************************************************ ************* -----Original Message----- From: paul smith [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 16, 2003 4:57 PM To: CF-Talk Subject: Re: Definition of a cached query At 04:18 PM 1/16/03 -0500, you wrote: >Could someone point me to what exactly is a cached query. It's kind of what it says. The record set is stored in memory for the specified time. As long as it hasn't expired, subsequent requests are pulled from memory. On SMARTERyellowpages.com for example, I cache a lot of queries for 5 minutes so a user paging "next 50" pulls data from memory - NOT the database. > Like once a use >cachedwithin is it pulling the exact data that it did before, or is it >going back to the datasource a little faster? What about if I am >passing parameters to it, does it have to cache each instance of that >query? It caches each instance of the same query when parameters vary. I've heard, that it will even chache an instance with the same parameters if the second query has identical functionality but is laid out a bit different. (Don't know if this is an urban legend.) best, paul >Robert Everland III >Web Developer Extraordinaire >Dixon Ticonderoga Company >http://www.dixonusa.com > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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
