> You can't really modify the contents of a cached query (again, assuming
that
> you're talking about using the caching attributes above). CF doesn't store
> those contents anywhere that you can programmatically access. To further
> illuminate this, let's say you run the following query:
>
> <cfquery name="foo" datasource="bar"
> cachedwithin="#CreateTimeSpan(0,1,0,0)#">
> SELECT fooval1, fooval2 from footable
> </cfquery>
>
> Then, perhaps you use one of the CF 3.x query functions:
>
> <cfscript>
> QueryAddRow(foo);
> QuerySetCell(foo, "fooval1", "new value 1");
> QuerySetCell(foo, "fooval2", "new value 2");
> </cfscript>
>
> Finally, when you reference the query, it would have your new row in it.
> However, what you've really modified is the query variable foo, not the
> underlying cached recordset, which CF stores after executing the query. CF
> doesn't let you touch this recordset directly, and will only reuse it if
> someone executes the same CFQUERY tag within the specified time span.
Does this mean that CF implicitly creates a copy of the cached query (query
variable foo, above) for every template that references the query or will CF
only do this if a template modifies the data within the query?
Jim
------------------------------------------------------------------------------
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.
