not if the query changes eg:
<CFQUERY NAME="myqry">
SELECT *
FROM my_table
WHERE user_id = '#attributes.user_id#'
</CFQUERY>
word of warning - in CF administrator you set the total number of queries
that CF will cache, but you can't define the amount of memory it will use -
too many big queries will bring down the box (at least it did last time i
checked)
Bert Dawson
ps I like the idea adding of the cftoken to the query, but was it suggested
by the javaphobic alan, or his javaphilic evil twin?
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: 05 October 2000 17:48
> To: Fusebox
> Cc: [EMAIL PROTECTED]
> Subject: RE: nwebie: pass lg array between templates
>
>
> Why would you need to dynamically name the query?
>
> If the returned data from one cached query to another
> is different, CF keeps track of which is which even
> when your template refers to them by the same name.
>
> best, paul
>
> At 08:03 AM 10/5/00 -0800, you wrote:
> >Another idea? If your server can handle it, you could
> dynamically name your
> >query, appending the CFTOKEN to the end of the query name.
> Cache the query
> >result, and when you need the query results again, they are
> cached so you
> >won't be double-hitting the SQL server.
> >
> >It would look like <CFQUERY name="qry_8123456" cachedwithin="20"> or
> >something like that.
>
> --------------------------------------------------------------
> ----------------
> To Unsubscribe visit
> http://www.houseoffusion.com/index.cfm?sidebar=lists&body=list
s/fusebox or send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body.
------------------------------------------------------------------------------
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.
