Except that, at least in current versions of CF, you can't cache queries that have cfqueryparams nor can you cache cfstoredprocs.
Doug -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Moretti Sent: Monday, September 25, 2006 10:14 AM To: [email protected] Subject: Re: [Reactor for CF] duckies has been merged > > I also had an interesting idea on how to speed up oo queries (at least after > their first run). First off, any given query is unique. That is to say > "Select * from User" is always "Select * from User" and is never "Select * > from FooBar". So, given that, I could hash the data used to create the > query and use that as a unique identifier for that query. This would allow > me to cache the query for reuse. > If I'm not mistaken this is how CF caches queries. If you pass a query of exactly the same statement and the query is cached then it uses the data from memory rather than requerying the database. I guess if you could some how turn on or off query caching through reactor, then CF should handle this for you. Of course you then get into the issue of how/when do you tell it to requery the database because the data has changed. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Reactor for ColdFusion Mailing List [email protected] Archives at: http://www.mail-archive.com/reactor%40doughughes.net/ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
