/me gets out the battering ram ;-)
No, you're right Charlie, I was referring to result sets and the
cachedwithin/cachedafter parameters of <cfquery>.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
"[T]he people can always be brought to the bidding of the leaders.
This is easy. All you have to do is to tell them they are being
attacked, and denounce the pacifists for lack of patriotism and
exposing the country to danger. It works the same in every country."
--Hermann Goering, Hitler's Reich-Marshall at the Nuremberg Trials
On Oct 3, 2006, at 4:03 PM, Charlie Arehart wrote:
At the risk of taking on Dean in a head-first ram-on-ram head
butt :-), I
want to offer a clarification.
Dean, you said "<cfqueryparam> explicitly prevents caching of
result sets",
and I think I know what you're getting at, but perhaps some may
misunderstand.
Use of CFQUERYPARAM doesn't "prevent caching of resultsets". It
does indeed
preclude the *use* of the CachedWithin or CachedAfter attributes in
CFQUERY
(in CFMX, that is, not in BlueDragon), so in that sense it
"prevents" you
trying to use cached results.
On the other hand, when Benjamin notes that use of CFQUERYPARAM
could lead
to seeming caching of results, I could see that *possibly* being
related to
an entirely different kind of caching: the caching within the
database of
the Query Execution Plan. CFQUERYPARAM does indeed cause the SQL
engine to
use "bind parameters" which lead the database to try to cache the
execution
plan for the query. That said, I don't think it should really cause
the
caching of the *resultset* ever returned from such a cached query
execution
plan, though someone with more experience may correct us on any of
these
matters.
I just wanted to put in a defense for what Benjamin may have been
getting
it, and clarify as well what Dean may have been meaning to say. OK,
that's
my volley, Dean (to switch analogies from rams to the revolution).
Fire away
while I reload my muzzle. :-)
/charlie
http://www.carehart.org/blog/
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dean H.
Saxe
Sent: Tuesday, October 03, 2006 2:10 PM
To: discussion@acfug.org
Subject: Re: [ACFUG Discuss] Issue with return from cfquery
Ben,
<cfqueryparam> explicitly prevents caching of result sets.
-dhs
Dean H. Saxe, CISSP, CEH
[EMAIL PROTECTED]
"What difference does it make to the dead, the orphans, and the
homeless,
whether the mad destruction is wrought under the name of
totalitarianism or
the holy name of liberty and democracy? "
--Gandhi
On Oct 3, 2006, at 1:41 PM, Benjamin Bloodworth wrote:
Maybe I have the wording wrong, but I have seen the exact same result
set returned when <cfqueryparam> was used in a query with different
values.
Breaking the connection in the datasource cleared it up.
Sql Server will also cache result sets if it gets requests for
what it
thinks is the exact same query.
-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------
-------------------------------------------------------------
To unsubscribe from this list, manage your profile @
http://www.acfug.org?fa=login.edituserform
For more info, see http://www.acfug.org/mailinglists
Archive @ http://www.mail-archive.com/discussion%40acfug.org/
List hosted by http://www.fusionlink.com
-------------------------------------------------------------
