Yes I have thought about it and it is not a bad idea by any means. However,
on code that makes use of the cfstoredproc tag, I was looking for a good way
to allow these to also get "cached" without having to go back into all the
code and switch the call from cfstoredproc to cfquery. Perhaps MM can add
this feature to the cfprocresult tag someday :-)

-----Original Message-----
From: Ricky Fritzsching [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 10:31 AM
To: CF-Talk
Subject: RE: cfstoredproc and cache

Mike:

Have you thought about using CFQUERY and then running the EXEC command
to run the store proc?

<cfquery name = "sp_YourName" datasource = "YourDSN" cachedwithin =
"#CreateTimeSpan(0,0,20,0)#">
    EXEC YourStoredProc
</cfquery>

  _____  

From: Tangorre, Michael [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 15, 2003 9:21 AM
To: CF-Talk

I tend to use stored procs even for "select" queries (especially ones
involving views, and many tables) and always use cfstoredproc over
calling
the procedures using cfquery. The downside is that there is no direct
way to
cache the result set(s). So... Yesterday I started working on a CFC to
load
a result set into either: session|application|server scope. The CFC has
a
few methods: refresh(), remove(), init(), and cacheIt(). Anyways, does
this
seem like a logical and organized approach to quasi-caching result sets
from
stored procs? I know I could just set the result set into the scope of
preference in the cfprocresult tag, but I thought the above was more
versatile and useful.

Am I missing something major here? Does anyone else do it a different
way?

Michael T. Tangorre

--------------------------------------------
Abacus Technology Corporation
Senior ColdFusion Developer
Advanced Certified ColdFusion MX Developer

8601 Georgia Avenue, Suite 400
Silver Spring, MD 20910
o. 301.495.4223
f. 301.562.9891
--------------------------------------------
  _____  

  _____  


[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]

Reply via email to