I realize that there's already been a lot of talk on the subject, but here's
what I think:
If the query is actually going to be cached (using the CACHEDWITHIN or
CACHEDAFTER attributes), then there is no reason to add it to either the
request or application scope. CFAS will handle the caching for you, and
will serve the cached query to anyone who requests it. The only issue I see
is that the query may be pushed out of the cache if the cache runs out of
room. In that case, the next execution of the CFQUERY tag will add it back
to the cache, so I don't see this as a big issue.
Comments?
Bob
-----Original Message-----
From: paul smith [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 02, 2000 12:28 AM
To: CF-Talk
Subject: Scope of Cached Query
What advantage is there for a cached query
to have Application vs Request scope?
best, paul
==============================
Paul Smith, Web/Database Droid
A: SupportNet, Inc, 3871 Piedmont Ave, Oakland, CA 94611
(There, there, there; there's, there, there....)
P: (510) 763-2358
C: (510) 205-6755
F: (510) 763-2370
E: [EMAIL PROTECTED]
W: http://www.support.net
----------------------------------------------------------------------------
--
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/cf_talk or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
