Right. This one I think I understand well enuf.
The question I have is whether there's any advantage in scoping a Query
cached in a CFQUERY tag as Application.GetListings contrasted with scoping
it as Request.GetListings.
In using the cached query in the application, I'm obviously only interested
in READS, so CFLOCKing of #Application.GetListings.MyVar# is not really
necessary, but recommended. If there's no advantage, then it seems simpler
and less prone error to simply scope the query as Request.GetListings
instead of pplication.GetListings.
best, paul
At 12:04 PM 10/2/00 -0400, you wrote:
>Second, cached queries aren't stored the same way as persistent memory
>variables are stored. That is, they're not simply identified by name. You're
>only going to have one variable called Request.GetListings (or
>Application.GetListings) and that variable will contain whatever you put
>into it. Query caching only comes into play when you execute a CFQUERY tag
>with a caching attribute - CF looks to see whether there's a matching
>recordset already cached.
------------------------------------------------------------------------------
Archives: http://www.mail-archive.com/[email protected]/
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.
