> So both the SQL (all statements) and the Query NAME must be
> IDENTICAL to the cached query?
>
> I would rather just run a blank (bare-bones SQL statement
> that returns just one or zero records) because the actual
> query returns 8,000 records and takes a few seconds to
> execute.
Yes, bo
nal Message-
> From: Brian Scandale [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, March 13, 2002 2:18 PM
> To: CF-Talk
> Subject: RE: Question About Query Caching
>
> Now I'm a bit confused...
>
> I thought that as long as the query had not expired that cf w
led by donkeys than by airplane crashes each year"
>
>
>-Original Message-
>From: Bud [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, March 13, 2002 1:27 PM
>To: CF-Talk
>Subject: RE: Question About Query Caching
>
>
>On 3/13/02, John Wilker penned:
>>My idea wo
al Message-
From: Bud [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 1:27 PM
To: CF-Talk
Subject: RE: Question About Query Caching
On 3/13/02, John Wilker penned:
>My idea would be to put a query with the same name on the page that
>updates the database. The new query will over
On 3/13/02, John Wilker penned:
>My idea would be to put a query with the same name on the page that
>updates the database. The new query will overwrite the cached one as
>long as the SQL is different, then the first time some one runs the real
>query it will re cache that one.
You mean as long a
My idea would be to put a query with the same name on the page that
updates the database. The new query will overwrite the cached one as
long as the SQL is different, then the first time some one runs the real
query it will re cache that one.
J.
John Wilker
Web Applications Consultant, and Aut
You can run the query with the cache set to 0 minutes:
cachedwithin= "#CreateTimeSpan(0,0,0,0)#"
-Original Message-
But what if I want it to show up right away? Is there a way to dump the
current cache as soon as a new item is inserted, so that the query is
re-cached the next time it is
7 matches
Mail list logo
