On the issue of query time outs, some of the queries which have time out are
really simple (e.g., select the top 2 rows, 10 fields from one table), so
it's not related to the query.
This started after our ISP moved the server to a new data center. All that
has changed are the IPs of the servers.
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 actual
> 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,
> 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 ca
uation?
Adrian
> -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
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 : 631
I don't think you can clear one query, but cfobjectcache will clear them
all.
Best check the docs on that one though because I'm just recalling it.
Adrian
> -Original Message-
> From: Robert Harrison [mailto:rob...@austin-williams.com]
> Sent: 11 February 2009 16:07
> To: cf-talk
> Subj
> if goo is stored is the application scope, and you place
> your query in
> the variables scope of goo, it's reliably cached for as
> long as goo is
> cached - you have control over it. If you cache the query
> using the
> cachedwithin attribute, it'll be cached for as long as the
> cachedwithin a
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]
[Donati
if goo is stored is the application scope, and you place your query in
the variables scope of goo, it's reliably cached for as long as goo is
cached - you have control over it. If you cache the query using the
cachedwithin attribute, it'll be cached for as long as the
cachedwithin attribute allows
It doesn't matter. CF caches queries based on the SQL string, not any
kind of variable. As long as you're thread safe without the
CACHEDWITHIN attribute, you'll be thread safe with it.
cheers,
barneyb
On Fri, 27 Aug 2004 00:01:33 -0400, Douglas Knudsen <[EMAIL PROTECTED]> wrote:
> Ok, I got a c
> 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
- 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 mor
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 CF
If I understand what you're doing ... I don't think is a caching issue, but
simply a matter of how your query is built, the app logic, or business rules
or something like that.
I think you'll want to figure out an application logic that suits your new
needs ...
For example, if it were me, I might
I'm not sure I understand your circumstances, but if one user has siteID=20
and another one has siteID=123, the query below will cache 2 record sets.
Happens all the time at www.SMARTERyellowpages.com (MANY cached queries there)
best, paul
At 01:24 PM 1/16/03 -0500, you wrote:
>Ok, I've been r
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:
SELECT sitename
FROM tblSites
WHERE siteID=#session.siteID#
Then you'll cache each query using a different siteid. This is done at
the SQL level (that exact
I believe you may be getting the scopes confused. Cached querys are
for most intents and purposes stored in some place equivalent to the
application scope. Your query also suggests that the information being
pulled is specific to the application, not the user (session). If
there is not any informat
I've been meaning to ask ...
what's more efficient, generally ... a stored procedure or a cached
query?
Also, for Joshua's question ... would a stored procedure be a better
alternative than a cached query, so that he gets faster execution, but
maintains his dynamic needs?
H.
> -Or
Why not simply store the query in the session scope? (This code assumes
MX and no need for locks.)
Then you can simply...
...
This also gives the added benefit of giving you a quick way to remove
the query:
Just remember that each session will have it's own query, so if your
sit
*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
02 4:43 PM
> To: CF-Talk
> Subject: RE: Query caching
>
>
> Thank you for your comments.
>
>
>type="EXCLUSIVE">
>
>
> SELECT lastname, firstname, party, state,
>
state#'
#session.temp.recordcount#
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: Que
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
To: "CF-Talk" <[EMAIL PROTECTED]>
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,
ovember 04, 2002 4:17 PM
> To: CF-Talk
> Subject: RE: Query caching
>
>
> Here's an example on CF 4.5:
>
>
> SELECTlastname, firstname, party, state,
> website, email
> FROMsenators
> WHERE state =
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 possi
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
ay, November 04, 2002 4:17 PM
> To: CF-Talk
> Subject: RE: Query caching
>
>
> Just store the query in session scope.
>
>
>
> -Original Message-
> From: Howie Hamlin [mailto:howie@;coolfusion.com]
> Sent: Monday, November 04, 2002 2:15 PM
> To: CF-Ta
Here's an example on CF 4.5:
SELECT lastname, firstname, party, state, website, email
FROMsenators
WHERE state = '#session.state#'
#session.temp.recordcount#
-Original Message-
From: Howie Hamlin [mailto:howie@;coolfusion.com]
Se
Just store the query in session scope.
-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 queries cached during a
session. I know that you c
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
> 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 templ
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
this:
The syntax
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
this:
The syntax is as follows:
... where the timespan arguments are days
> Well, er, yes. That's what I mean by a cached query.
> In there another way to cache a query?
Well you could scope it into a session, or application scope and then wrap
your query in an isdefined statement, and then you could control when that
query is refreshed a little better.
>
> At 08:09
Well, er, yes. That's what I mean by a cached query.
In there another way to cache a query?
best, paul
At 08:09 AM 10/2/00 -0500, you wrote:
>Have you tried adding CachedWithin=#CreateTimeStamp(0,0,10,0)#
>
>Add this to your query and then it will cache the query when it runs so it
>does not h
Have you tried adding CachedWithin=#CreateTimeStamp(0,0,10,0)#
Add this to your query and then it will cache the query when it runs so it
does not have to requery again.
Larry Juncker
Senior Cold Fusion Programmer
Heartland Internet
-Original Message-
From: Jon Hall [mailto:[EMAIL PROTE
get the next 20?
HTH
Dick
>Thanks for your help
>jon
>
>
>- Original Message -
>From: "Dick Applebaum" <[EMAIL PROTECTED]>
>To: "CF-Talk" <[EMAIL PROTECTED]>
>Sent: Saturday, September 30, 2000 8:08 AM
>Subject: Re: query cachin
CF caches dynamic queries, too. It includes the SQL to distinguish one
dynamic query from another.
For example, since #REQUEST.alpha# has the value of each of the 26 letters
in the alphabet, the following query is chached in 26 different Queries,
even though in my CF code I refer to all as RE
t; <[EMAIL PROTECTED]>
To: "CF-Talk" <[EMAIL PROTECTED]>
Sent: Saturday, September 30, 2000 8:08 AM
Subject: Re: query caching?
> Depending on the totality of what you anticipate is going to be
> happening at any given time, you can:
>
> 1) let CF cache the queries...
Yeah.
By the way these columns are searched (and named) it indicates that
they likely (pun intended) contain multiple values:
RecordID #00022 Keywords='this,that,another...'
A column with multiple values violates the first normal form: each column
should be atommic.
or anot
On 9/30/00, Dick Applebaum penned:
>Hmmm... 10 seconds to query sounds like some db redesign may be in order.
>
>This will vary with the db engine, but there are things you can do.
>
>I noticed that your db is denormalized (ProductsCategory,
>ProductsKeyWords, and maybe ProductsStyleNumber). If y
Depending on the totality of what you anticipate is going to be
happening at any given time, you can:
1) let CF cache the queries... this is especially good if you
anticipate that there will be a lot of similar queries as in
drill-downs, or several users making identical queries (skewed
popul
server (which I assume would be done on each request for the query.)
>>>
>>>Another thing to keep in mind is that if the data is SESSION SPECIFIC, i.e.
> >>a user's permissions or something along those lines, how would you use
>>>CachedWithin? There's
>It's quite possible to declare a query directly into any of the scope's
>available to your application except Client (unless of course you serialize
>the query w/ wddx.) This is a valid call:
>
>Resulting in Session.myQuery being cached for the duration of the session.
yeah, thanks. i was just b
work for
>>that data just as it does for all other session specific data.
>>
>>I think the latter point is more relevant than the first, but that just's my
>>opinion. ;-)
>>
>>Jason
>>
>>-Original Message-
>>From: Dick Applebaum
hat just's my
>opinion. ;-)
>
>Jason
>
>-Original Message-
>From: Dick Applebaum [mailto:[EMAIL PROTECTED]]
>Sent: Friday, April 14, 2000 7:43 AM
>To: [EMAIL PROTECTED]
>Cc: [EMAIL PROTECTED]
>Subject: RE: Query Caching
>
>
>A little different
s more relevant than the first, but that just's my
opinion. ;-)
Jason
-Original Message-
From: Dick Applebaum [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 14, 2000 7:43 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Query Caching
A little different twist on this threa
ut that just's my
opinion. ;-)
Jason
-Original Message-
From: Dick Applebaum [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 14, 2000 7:43 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Query Caching
A little different twist on this thread.
Several people have suggested
ll:
>
>
>
>Resulting in Session.myQuery being cached for the duration of the session.
>
>-Original Message-
>From: Emily B. Kim [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, April 13, 2000 12:05 PM
>To: [EMAIL PROTECTED]
>Subject: Re: Query Caching
>
>
>
--Original Message-
From: Emily B. Kim [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 13, 2000 12:05 PM
To: [EMAIL PROTECTED]
Subject: Re: Query Caching
>Is it possible to cache a query only for a particular user for only the
>length of his or her session?
>I have a query that generates a
ng underwater.
>
>Feeling better?
>
>
>- Original Message -
>From: "Judah McAuley" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Thursday, April 13, 2000 11:25 AM
>Subject: Re: Query Caching
>
>
>> At 11:23 AM 4/
, 2000 12:25 PM
To: [EMAIL PROTECTED]
Subject: Re: Query Caching
At 11:23 AM 4/13/00 -0400, you wrote:
>Yes. You can save the query to SESSION scope.
>
>
>
>
> SQL STUFF
>
>
>
>
>HTH!
>Sh
l Message -
From: "Judah McAuley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, April 13, 2000 11:25 AM
Subject: Re: Query Caching
> At 11:23 AM 4/13/00 -0400, you wrote:
> >Yes. You can save the query to SESSION scope.
> >
> >
> >
PROTECTED]
Subject: Re: Query Caching
At 11:23 AM 4/13/00 -0400, you wrote:
>Yes. You can save the query to SESSION scope.
>
>
>
>
> SQL STUFF
>
>
>
>
>HTH!
>Sharon
One problem I worry abo
No, it's client variables that can be stored in Registry. Session
variables are held in RAM for the duration of a session. And I've done
applications with extensive use of session scoped queries, structures, etc,
and haven't significantly impacted the RAM requirements of the server.
Also, a gre
> One problem I worry about with this: Session variables are
> frequently stored in the Registry on NT machines, yes?
No, session variables are always stored in memory. Client variables may be
stored in the registry, in a database, or in a cookie on the client.
Dave Watts, CTO, Fig Leaf Softwar
>One problem I worry about with this: Session variables are frequently
>stored in the Registry on NT machines, yes? So if you had a very large
>query, or quite a few users, you are potentially packing a lot of info into
>the registry. Perhaps unwise.
actually, session variables are stored i
At 11:23 AM 4/13/00 -0400, you wrote:
>Yes. You can save the query to SESSION scope.
>
>
>
>
> SQL STUFF
>
>
>
>
>HTH!
>Sharon
One problem I worry about with this: Session variables are frequently
stored in the Registr
Name your query in the Session Scope:
select blah
I would do this in the application.cfm to make sure it's always available,
but make sure it only runs once per session:
I wouldn't worry about taking a memory hit, unless the query is returning
thousands of records (which w
>Is it possible to cache a query only for a particular user for only the
>length of his or her session?
>I have a query that generates a roles & privileges packet that applies only
>to the current session and user. When the session expires so does the cached
>query.
>What the memory load differenc
Yes. You can save the query to SESSION scope.
SQL STUFF
HTH!
Sharon
At 10:22 AM 4/13/2000 -0400, Duane Boudreau wrote:
>Hi All,
>
>Is it possible to cache a query only for a particular user for only the
>length of hi
63 matches
Mail list logo
