At 02:30 PM 10/13/00 +1100, you wrote:
>Paul,
>
>What do you mean when you say that "Request-scoped cached queries are
>available after
>the page request"? Certainly the results of the query are cached by CFAS.
>But this has nothing to do with the request-scope, or even the query name.
I was just pointing out that Request-scoping didn't always mean the object
was gone after the page request was completed.
>If I run two queries, but with DIFFERENT names, and ask for the first to be
>cached, then the SECOND query will come from the cache, even though the
>name/scope is different. CFAS is just looking at the SQL when it comes to
>cacheing - it doesn't care about who 'ran' the query, what it was called, or
>anything of the kind.
In the above I assume you mean both queries have the same SQL. I had not
seen your observation made before. I was aware that multiple queries with
the SAME name, but different SQL, were cached separately. In other words,
I did know CFAS associates SQL with the underlying dataset. But looking at
it, I see your observation does make sense.
I guess you're going to tell me now that scoping a cached query with
Request scope has no effect on locking. That is, you don't have to lock
data from a cached query no matter how it's scoped. Is this right? (I was
thinking request-scoping cached queries enabled me to avoid locking entirely.)
best, paul
>Or am I a complete idiot? (always possible)
Hardly.
>Lee (Bjork) Borkman
>http://bjork.net ColdFusion Tags by Bjork
>
>
>-----Original Message-----
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
>One small wrinkle. Request-scoped cached queries are available after
>the page request. I'm not sure of the precise description of what's going
>on in this case. That is, I'm not sure if it's accurate to say the
>Request-scoped cached query persists after the page request.
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
