Ok, I've been reading up on query caching today and I think I've run
into something that may cause me problems unless there is a way to
dynamically name queries.
I have an application that houses data for multiple sites - the data
is referenced by a siteID that is set as a session variable.
So
PROTECTED]]
Sent: Thursday, January 16, 2003 12:25 PM
To: CF-Talk
Subject: Query Caching Question
Ok, I've been reading up on query caching today and I think
I've run into something that may cause me problems unless
there is a way to dynamically name queries.
I have an application
.
-Original Message-
From: Joshua Miller [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 10:25 AM
To: CF-Talk
Subject: Query Caching Question
Ok, I've been reading up on query caching today and I think I've run
into something that may cause me problems unless there is a way
I believe you may be getting the scopes confused. Cached querys are
for most intents and purposes stored in some place equivalent to the
application scope. Your query also suggests that the information being
pulled is specific to the application, not the user (session). If
there is not any
Well, you can't dynamically name queries, but remember that query
caching requires the EXACT same SQL to be used.
So if you do this:
cfquery name=qGetSite cachedwithin...
SELECT sitename
FROM tblSites
WHERE siteID=#session.siteID#
/cfquery
Then you'll cache each query using a different siteid.
I'm not sure I understand your circumstances, but if one user has siteID=20
and another one has siteID=123, the query below will cache 2 record sets.
Happens all the time at www.SMARTERyellowpages.com (MANY cached queries there)
best, paul
At 01:24 PM 1/16/03 -0500, you wrote:
Ok, I've been
6 matches
Mail list logo
