The default limit in CF Admin for cached queries is 100. We do cache
queries, but have had some issues with query timeout.
Is there a larger limit I can set that would be reasonable?
Robert B. Harrison
Director of Interactive services
Austin Williams
125 Kennedy Drive, Suite 100 Hauppauge
be .
-Original Message-
From: Robert Harrison [mailto:rob...@austin-williams.com]
Sent: Thursday, February 19, 2009 9:15 AM
To: 'cf-talk@houseoffusion.com'
Subject: Query Caching Limit?
The default limit in CF Admin for cached queries is 100. We do cache
queries, but have had some issues
/0CF7D323BBC1
Bug tracker:http://jira.jboss.org/jira/browse/RAILO
Railo Blog: http://www.railo-technologies.com/blog
-Ursprüngliche Nachricht-
Von: Robert Harrison [mailto:rob...@austin-williams.com]
Gesendet: Donnerstag, 19. Februar 2009 15:20
An: cf-talk
Betreff: RE: Query Caching Limit
I have a huge query that is used in a timed loop process completes. The
process could take from a minute to 15 hours, and it runs the query each
time is goes through a loop.
If I cache the query (cached within the last 15 hours), it can save a lot of
re-querying processing... but what if the
: Query Caching Function: Clearing Cached Query
I have a huge query that is used in a timed loop process completes. The
process could take from a minute to 15 hours, and it runs the query
each
time is goes through a loop.
If I cache the query (cached within the last 15 hours), it can save
I looked in the docs first.
What if at the end of the process I ran the query using the same query name
and no caching. Would that actually get rid of the cached query?
Robert B. Harrison
Director of Interactive services
Austin Williams
125 Kennedy Drive, Suite 100 Hauppauge NY 11788
T :
-Original Message-
From: Robert Harrison [mailto:rob...@austin-williams.com]
Sent: 11 February 2009 16:23
To: cf-talk
Subject: RE: Query Caching Function: Clearing Cached Query
I looked in the docs first.
What if at the end of the process I ran the query using the same query
name
I wonder if it also needs the same params, doesn't CF8 allow cached queries
with cfqueryparam? Maybe change the param to something that'll return an
empty result.
CF 8 does allow cached queries with CFQUERYPARAM. However, it requires
the bound parameter values to match before it uses the
What if at the end of the process I ran the query using the same query name
and no caching. Would that actually get rid of the cached query?
That won't work, but you can flush a single query from the cache by
rerunning the query with only one change - set CACHEDWITHIN to
CreateTimeSpan(0, 0,
even whitespace inside sql statement must be the same! so mind those
tabs/spaces in your code formatting...
Azadi Saryev
Sabai-dee.com
http://www.sabai-dee.com/
Dave Watts wrote:
What if at the end of the process I ran the query using the same query name
and no caching. Would that actually
Running into some odd behavior, that maybe someone can give me insight
on. On CF8, connecting to MS SQL, I'm seeing some very odd situations,
whereby my query results are being cached, even though I haven't coded
them to be. I run a template, that dumps query results, and get 23
values back. I
Thanks everyone for your input.
- Paul
Hello everyone,
First post here, so don't get too hard on me.
I'm developping a small e-commerce application with less than 1000
products ( around 700).
As far as I know, only product prices would be updated on a weekly
basis.
I'm not too
Hello everyone,
First post here, so don't get too hard on me.
I'm developping a small e-commerce application with less than 1000 products (
around 700).
As far as I know, only product prices would be updated on a weekly basis.
I'm not too sure how to handle caching.
So here is my question. Is
with a timeout of say 6
days.
Hope this helps.
Doug B.
- Original Message -
From: Paul Boyd [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Sunday, November 12, 2006 4:05 AM
Subject: Advice about query caching
Hello everyone,
First post here, so don't get too hard on me.
I'm
: Paul Boyd [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Sunday, November 12, 2006 4:05 AM
Subject: Advice about query caching
Hello everyone,
First post here, so don't get too hard on me.
I'm developping a small e-commerce application with less than 1000
products ( around
.
- Original Message -
From: Paul Boyd [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Sunday, November 12, 2006 4:55 AM
Subject: Re: Advice about query caching
Thanks Doug,
Your feedback is greatly appreciated.
Could you tell me why storing a recordset in an application variable
this
communication are not necessarily those expressed by Reed Exhibitions.
Visit our website at http://www.reedexpo.com
-Original Message-
From: Doug Brown
To: CF-Talk
Sent: Sun Nov 12 13:14:10 2006
Subject: Re: Advice about query caching
Cachedwithin does load the dataset into server memory
cachedwithin?
- Original Message -
From: Robertson-Ravo, Neil (RX) [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Sunday, November 12, 2006 6:14 AM
Subject: Re: Advice about query caching
It shouldn't have to be calling into the app scope for every request -
only
?
- Original Message -
From: Robertson-Ravo, Neil (RX) [EMAIL PROTECTED]
To: CF-Talk cf-talk@houseoffusion.com
Sent: Sunday, November 12, 2006 6:14 AM
Subject: Re: Advice about query caching
It shouldn't have to be calling into the app scope for every request -
only
the
intended recipient
Huh? Once it's in the Application scope it can stay there for as long
as you want.
On 11/12/06, Doug Brown [EMAIL PROTECTED] wrote:
Cachedwithin does load the dataset into server memory but stays there until
it times out, and then refreshes. Setting it in the application scope
requires you to
about query caching
Huh? Once it's in the Application scope it can stay there for as long
as you want.
On 11/12/06, Doug Brown [EMAIL PROTECTED] wrote:
Cachedwithin does load the dataset into server memory but stays there
until
it times out, and then refreshes. Setting it in the application scope
://www.reedexpo.com
-Original Message-
From: James Holmes
To: CF-Talk
Sent: Sun Nov 12 13:50:29 2006
Subject: Re: Advice about query caching
Huh? Once it's in the Application scope it can stay there for as long
as you want.
On 11/12/06, Doug Brown [EMAIL PROTECTED] wrote
To: CF-Talk
Sent: Sun Nov 12 14:13:51 2006
Subject: Re: Advice about query caching
Oh agreed - it's often better use of resources to query the DB rather
than to perform elaborate caching when each user needs different
results etc. It depends on how big the query is, how much memory is in
the server
I'm going to to quote Ben Forta (et al) here:
ColdFusion is not a database server
If you intend to do frequent, perhaps complex QoQ on the query in
memory, you may be better off simply going to the DB. Multiple calls
to the DB in a page will reuse the same DB connection and for most
purposes CF
://www.reedexpo.com
-Original Message-
From: James Holmes
To: CF-Talk
Sent: Sun Nov 12 14:13:51 2006
Subject: Re: Advice about query caching
Oh agreed - it's often better use of resources to query the DB rather
than to perform elaborate caching when each user needs different
results etc
Could you tell me why storing a recordset in an application
variable is not recommended. I saw this technique used
several times, and prefered over the cachedWithin method.
Apparently it's easier to control, to flush the cache, and I
guess you could use Cfqueryparam as well.
There is
You should never store database information into a memory
variable unless it is within your shopping cart and then I
would store it as a array.
I'm sorry, but this is simply wrong.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
Fig Leaf Software provides the highest caliber
I'm not too sure how to handle caching.
So here is my question. Is it appropriate to store the
products recordset in an application variable within
onApplicationStart, and use QoQ for for data manipulation
in my different templates ?
Any query that has significant reuse potential as-is,
Paul,
I think your method would certainly work, however my experience with
e-commerce has been that the full recordset of products is almost
never used. By using QoQ against your full recordset, you do limit
yourself in some of the functions like true full-text searching that
the
I have a query counting records in a 25 million plus database. Even with
indexing and what not it takes about 25 seconds to run this query. (count *
from table where date 19000101) Is there a way I could cache the query so
that if it is ran in that same way it very quickly returns the full count.
Hi Jeremy,
Yes, you can very easily cache queries using the cachedwithin=
attribute of cfquery
Like so:
cfquery datasource=mydata name=myquery
cachedwithin=#createTimeSpan( 1, 0, 0, 0 )#
SELECT COUNT( * ) FROM myTable WHERE myDate '1900-01-01'
/cfquery
This will cache your query for
The only problem with this is the query can change due to the dynamic
building of the where clause. Could do a cached query that selects
everything that could be in the where clause then do QoQ on that for dynamic
where clause needs. I'd just be a little fearful of how much would need to
be
On 3/17/06, Jeremy Bunton [EMAIL PROTECTED] wrote:
I have a query counting records in a 25 million plus database. Even with
indexing and what not it takes about 25 seconds to run this query. (count *
from table where date 19000101) Is there a way I could cache the query so
that if it is ran
know I
can't fit the whole record set in ram.
Jeremy
-Original Message-
From: Aaron Rouse [mailto:[EMAIL PROTECTED]
Sent: Friday, March 17, 2006 9:44 AM
To: CF-Talk
Subject: Re: Large count query caching
The only problem with this is the query can change due to the dynamic
building
If you were taking the route of a cached query then yes/no that you are
wrong. If the count() is going to change based upon the where clause then
you would have to have a single master cached query that pulled out
everything possibly needed so that you could then do QoQ on that for the
dynamic
To: CF-Talk
Subject: Large count query caching
I have a query counting records in a 25 million plus database. Even with
indexing and what not it takes about 25 seconds to run this query.
(count * from table where date 19000101) Is there a way I could cache
the query so that if it is ran in that same
PROTECTED]
Sent: Friday, March 17, 2006 10:08 AM
To: CF-Talk
Subject: Re: Large count query caching
If you were taking the route of a cached query then yes/no that you are
wrong. If the count() is going to change based upon the where clause then
you would have to have a single master cached query
index seems to go. I need oracle's bitmap indexes I think to do it
right. I'm pretty sure my indexes are ok.
Jeremy
-Original Message-
From: mark [mailto:[EMAIL PROTECTED]
Sent: Friday, March 17, 2006 10:43 AM
To: CF-Talk
Subject: RE: Large count query caching
Is there a finite number
:43 AM
To: CF-Talk
Subject: RE: Large count query caching
Is there a finite number of options for a count? Even if the number is
50,
you could run the queries late at night and cache the results for 24
hours?
It wouldn't take any shorter time, but to the user it would be much
better
oddly enough the more ands in the where clause
the faster the
clustered index seems to go.
That does seem odd, but that's the way it usually works. The 'ands' are
cutting off chunks of data from the whole, and making the search cover
smaller areas. Also, if your 'ands' are part of your
Message-
From: Jeremy Bunton [mailto:[EMAIL PROTECTED]
Sent: Friday, March 17, 2006 8:28 AM
To: CF-Talk
Subject: Large count query caching
I have a query counting records in a 25 million plus database. Even with
indexing and what not it takes about 25 seconds to run this query. (count *
from table
I'll check that out, I am not using them now.
Jeremy
-Original Message-
From: Mark A Kruger [mailto:[EMAIL PROTECTED]
Sent: Friday, March 17, 2006 11:09 AM
To: CF-Talk
Subject: RE: Large count query caching
If you cannot cache on the web server - make sure and bind the data using
) FROM myTable
With the * it has to return all records and all fields.
-Original Message-
From: Jeremy Bunton [mailto:[EMAIL PROTECTED]
Sent: Friday, March 17, 2006 9:28 AM
To: CF-Talk
Subject: Large count query caching
I have a query counting records in a 25 million plus
: Friday, March 17, 2006 10:29 AM
To: CF-Talk
Subject: Re: Large count query caching
Hi Aaron,
Are you sure about that?
I just tried three different queries (count(*), count(field) and
count(0)) on two joined tables with a date selection which return a
count of about 50 records.
all three queries
Wolfe, Aaron wrote:
You should use a field name in the count instead of the *. It should
speed it up.
SELECT COUNT( fieldname ) FROM myTable
With the * it has to return all records and all fields.
COUNT(fieldname) has a different meaning then COUNT(*).
Jochem
Aaron Rouse wrote:
What is a bitmap index?
The short explanation:
Most types of database index contain the value of the indexed
field plus a pointer to the rest of the row. So if you are
indexing a bigint, that is 8 bytes for the value, another 8 bytes
for the pointer and some room for
: Large count query caching
Aaron Rouse wrote:
What is a bitmap index?
The short explanation:
Most types of database index contain the value of the indexed
field plus a pointer to the rest of the row. So if you are
indexing a bigint, that is 8 bytes for the value, another 8 bytes
for the pointer
Hi,
Sorry for asking a JSP question here but I have not been able to find a
mailing as good as CFTALK for Java/JSP issues.
I am in the process of converting a CF application over to JSP running under
WebLogic as practice to see how long it takes to do the same coding vs. using
CFMX.
In my CF
You can just stash the recordset in the application scope, much like
you would in CF.
c:set var=myRecordSet scope=application value=${recordset} /
or if you're not using JSTL
% application.setAttribute(myRecordSet, recordset) %
cheers,
barneyb
On Mon, 3 Jan 2005 17:43:57 -, Ciliotta,
named goo.Inside goo I perform a query.Now this cfc goo
has an instance stored in the application scope.I want to employ query
caching on that query via the cfquery tags cachedwithin attribute.
Something tells me this no so good for thread safteyness, eh?Thoughts?
Yes, I var scoped the query
an instance stored in the application scope.I want to employ query
caching on that query via the cfquery tags cachedwithin attribute.
Something tells me this no so good for thread safteyness, eh?Thoughts?
Yes, I var scoped the query name.Is it the fact that CF uses the name,
sql, and dsn to ID
that's what I figured...danke
--
---
Douglas Knudsen
http://www.cubicleman.com
If you don't like something, change it. If you can't change it, change your attitude. Don't complain. - Maya Angelou
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
this cfc goo
has an instance stored in the application scope.I want
to employ query
caching on that query via the cfquery tags cachedwithin
attribute.
Something tells me this no so good for thread safteyness,
eh?Thoughts?
Yes, I var scoped the query name.Is it the fact that CF
uses the name
Ok, I got a cfc named goo.Inside goo I perform a query.Now this cfc goo
has an instance stored in the application scope.I want to employ query
caching on that query via the cfquery tags cachedwithin attribute.
Something tells me this no so good for thread safteyness, eh?Thoughts?
Yes, I var scoped
Is there any documentation on how to handle cached queries
across a load balanced environment?
No, not to my knowledge.
I've noticed some oddities on ours, and was wondering if we
were missing something obvious.
Could you be more specific? Are you referring to caching queries using the
I have a 'Telemarketing' application, don't worry we only call existing
customers to update there profile information for the new sales process,
that caches a list of the first 50 customers based on the search criteria.
This works great for now, but we are adding a second person to make calls at
, 2003 1:03 PM
To: CF-Talk
Subject: Query Caching
I have a 'Telemarketing' application, don't worry we only call existing
customers to update there profile information for the new sales process,
that caches a list of the first 50 customers based on the search criteria.
This works great
No they wont. Query caching takes more than the query name into account.
Think of the sql string and the cfquery parameters as a
hash that CF uses to look up to see if the query is in it's cache. If
the parameters _and_ the string match exactly then the query will be
pulled from cache, otherwise
- Field Support Team
RDO Equipment Co.
Phone (701) 239-8755
[EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
-Original Message-
From: jon hall [mailto:[EMAIL PROTECTED]]
Sent: Thursday, January 30, 2003 3:58 PM
To: CF-Talk
Subject: Re: Query Caching
No they wont. Query caching takes more than
it as the user pages through their results.
However, that still means that as each page gets loaded, the query still needs to be
run.
It is my understanding of/experience with query caching that results are cached based
on the name of the query, and not the actual guts of the query, so having
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
| needs to get run again? Should I do something like append the
| CFTOKEN for that user's session to the query name so that it is
| unique? Or should I store the query output as an array in a session
| variable?
store them in a session structure
-
From: Pete Ruckelshaus [EMAIL PROTECTED]
Date: Fri, 17 Jan 2003 09:02:22 -0500
Subject: Next N Navigation and query caching theory question
Hi,
I am rebuilding my employer's bug tracking application; quite a job,
but it's been fun (seriously, plus I get to be a hero to hundreds of
developers who
It is my understanding of/experience with query caching that results are
cached based on the name of the query, and not the actual guts of the
query, so having multiple users each with their own dynamic queries but all
run under the same query name will mean that only the first cached query
that as each page gets loaded, the
query still needs to be run.
It is my understanding of/experience with query caching that results are
cached based on the name of the query, and not the actual guts of the
query, so having multiple users each with their own dynamic queries but
all run under the same
Instead of querying all the data for the entire list on every page (even
with caching), you an often get better results by just querying the primary
keys first, and then query the data for the 50 records you're displaying in
this page--filter by primary key is very fast. Then pass the complete
Interesting. That's basically what I do at SMARTERyellowpages.com for
full-text queries, except I store the list of primary keys in a cached
query. For example, using office as a search term in
www.SMARTERyellowpages.com I find 1941 Listings that I can page thru 50 at
a time.
For drill-down
I should also point out that when I used the primary key caching technique
I was doing a full-text search against a Verity collection to return the
primary keys and then using those to get the details out of a database. So
in my particular case, I had to do two queries (one against verity, one
Ok, I've been reading up on query caching today and I think I've run
into something that may cause me problems unless there is a way to
dynamically name queries.
I have an application that houses data for multiple sites - the data
is referenced by a siteID that is set as a session variable.
So
PROTECTED]]
Sent: Thursday, January 16, 2003 12:25 PM
To: CF-Talk
Subject: Query Caching Question
Ok, I've been reading up on query caching today and I think
I've run into something that may cause me problems unless
there is a way to dynamically name queries.
I have an application
.
-Original Message-
From: Joshua Miller [SMTP:[EMAIL PROTECTED]]
Sent: Thursday, January 16, 2003 10:25 AM
To: CF-Talk
Subject: Query Caching Question
Ok, I've been reading up on query caching today and I think I've run
into something that may cause me problems unless there is a way
information coming back from the query specific to
the user then I don't see a problem...
If the query does actually have user specific information, you may be
better off just adding a userid field to the query. Caching it isn't a
problem then.
cfquery datasource=#request.dsn# name=qGetSite
SELECT
Well, you can't dynamically name queries, but remember that query
caching requires the EXACT same SQL to be used.
So if you do this:
cfquery name=qGetSite cachedwithin...
SELECT sitename
FROM tblSites
WHERE siteID=#session.siteID#
/cfquery
Then you'll cache each query using a different siteid
reading up on query caching today and I think I've run
into something that may cause me problems unless there is a way to
dynamically name queries.
I have an application that houses data for multiple sites - the data
is referenced by a siteID that is set as a session variable.
So for example
I have an application where I would like one or two queries cached during a session.
I know that you can use
cachedwithin to cache a query globally for an application but I don't think that would
be based on session...
So, is it possible to cache a query for a session? If so, a small code
Just store the query in session scope.
cfquery name=SESSION.qMyQuery datasource=yadayada
-Original Message-
From: Howie Hamlin [mailto:howie;coolfusion.com]
Sent: Monday, November 04, 2002 2:15 PM
To: CF-Talk
Subject: Query caching
I have an application where I would like one or two
#session.temp.recordcount#/CFOUTPUT
-Original Message-
From: Howie Hamlin [mailto:howie;coolfusion.com]
Sent: Monday, November 04, 2002 4:15 PM
To: CF-Talk
Subject: Query caching
I have an application where I would like one or two queries cached during a
session. I know that you can use
;teleplanwireless.com]
Sent: Monday, November 04, 2002 4:17 PM
To: CF-Talk
Subject: RE: Query caching
Just store the query in session scope.
cfquery name=SESSION.qMyQuery datasource=yadayada
-Original Message-
From: Howie Hamlin [mailto:howie;coolfusion.com]
Sent: Monday, November 04, 2002 2
I had a feeling it was something like that but I wanted to make sure.
Thanks,
Howie
- Original Message -
From: Haggerty, Mike [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, November 04, 2002 4:17 PM
Subject: RE: Query caching
Here's an example on CF 4.5:
CFQUERY NAME
Howie Hamlin wrote:
I have an application where I would like one or two queries cached
during a session. I know that you can use
cachedwithin to cache a query globally for an application but I don't
think that would be based on session...
cachedwithin is server-wide.
So, is it possible
-Talk
Subject: RE: Query caching
Here's an example on CF 4.5:
CFQUERY NAME=senate DATASOURCE=resource
SELECTlastname, firstname, party, state,
website, email
FROMsenators
WHERE state = 'CFOUTPUT#session.state#/CFOUTPUT'
/CFQUERY
]
Sent: Monday, November 04, 2002 4:30 PM
Subject: Re: Query caching
So, is it possible to cache a query for a session?
Why would you want to? Caching looks at both the name and the SQL
statement. If they are the same, wouldn't the outcome be the same as well?
Jochem
I'll make sure our developer uses the locks...
Thanks,
Howie
- Original Message -
From: Raymond Camden [EMAIL PROTECTED]
To: CF-Talk [EMAIL PROTECTED]
Sent: Monday, November 04, 2002 4:33 PM
Subject: RE: Query caching
This example is missing locking. Sorry if I sound like a broken
#session.temp.recordcount#/CFOUTPUT
Happy now?
Hoping I did this right,
M
-Original Message-
From: Raymond Camden [mailto:jedimaster;macromedia.com]
Sent: Monday, November 04, 2002 4:33 PM
To: CF-Talk
Subject: RE: Query caching
This example is missing locking. Sorry if I sound like a broken
it is. - Yoda
-Original Message-
From: Haggerty, Mike [mailto:MHaggerty;mbda.gov]
Sent: Monday, November 04, 2002 4:43 PM
To: CF-Talk
Subject: RE: Query caching
Thank you for your comments.
cfif NOT isdefined(session.temp)
cflock name=data_6 throwontimeout=Yes
*EXPLICATIVE*
Thanks
M
-Original Message-
From: Raymond Camden [mailto:jedimaster;macromedia.com]
Sent: Monday, November 04, 2002 5:05 PM
To: CF-Talk
Subject: RE: Query caching
Nope - sorry. :)
Your isdefined check needs a read lock around it.
Quick code that my have typos+pseudo
Let's say I have a query that is cached ...
Let's say a user adds a new item to the table called in the query.
Now we all know that so long as the query is cached, the new item won't show
up in the output.
But what if I want it to show up right away? Is there a way to dump the
current cache
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
-Talk
Subject: Question About Query Caching
Let's say I have a query that is cached ...
Let's say a user adds a new item to the table called in the query.
Now we all know that so long as the query is cached, the new item won't
show up in the output.
But what if I want it to show up right away
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 as
-
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 overwrite the cached one
-
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 overwrite the cached
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 would return
the cashed results... regardless
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, both the
Quick question!
When using the cachedwithin parameter of the cfquery, can someone remind
me is this cached per client or by application? It has escaped me, if it
was cached for everyone or not.
Regards,
Andrew Scott
~~
Your ad could be here.
Andrew Scott wrote:
Quick question!
When using the cachedwithin parameter of the cfquery, can someone remind
me is this cached per client or by application? It has escaped me, if it
was cached for everyone or not.
For everyone.
Jochem
~~
=get_content datasource=#request.www_ds# maxrows=1
dbtype=ODBC cachedwithin=#CreateTimeSpan(1,0,0,0)#
... where the timespan arguments are days,hours,minutes,seconds.
- Original Message -
Just a quick question about query caching (using CACHEDWITHIN attrib) --
Is the cached query tied
17, 2001 4:32 PM
To: CF-Talk
Subject: Re: Query Caching..
The cached query will persist for the template it was run from, and the only
way to override it (even if CF gets newer info from the database in an
identical query elsewhere) is to use the cfobjectcache tag (5.0 only) like
Ahh, so basically caching a query with the same name and
application within
an application that uses different templates (e.g. dsp_list.cfm and
dsp_list2.cfm) but the same query is pointless?
NO - a Cached query persists for the same SQL and datasource, it has nothing
to do with the template
someone goes through the trouble of tracing the URL's so what? The
only variable they'll see is worthless as far as getting any important data.
Crap, who cares what variables I'm using? All I'm trying to do is get some
help about how to fix this query caching problem, and I'm getting attacked
over
o: CF-Talk
Subject: Re: Stop query caching UPDATE
Josh R wrote:
PLEASE READ CAREFULLY
(Technical info - Using CF 4.5.2 to query MS Access 97 SR2 database for
a
text field and date field for unknown number of recordnumbers)
OK. I have flushed the query by making a dynamically changing
1 - 100 of 124 matches
Mail list logo
