Bible" cites a method for caching a single result set stored procedure, as
follows:
<cfquery name="cached_12hours" datasource="#dsn#"
cachedwithin="#createtimespan(0,12,0,0)#">
{ CALL sp_getAuthors('Churvis') }
</cfquery>
~Dina
----- Original Message -----
From: Robertson-Ravo, Neil (RX)
To: CF-Talk
Sent: Thursday, September 30, 2004 1:01 AM
Subject: RE: CFStoredProc vs CFQuery
Yeah if you must cache, then use CFQUERY but you can also just duplicate
the
results into a new query object and cache that.
_____
From: Dave Watts [mailto:[EMAIL PROTECTED]
Sent: 29 September 2004 20:35
To: CF-Talk
Subject: RE: CFStoredProc vs CFQuery
> Are there any benefits to calling stored procedures using
> CFStoredProc vs. CFQuery? All the stored procs return a
> single record set.
>
> The limitation I am running in to is how to cache the results
> of a query that is created calling CFStoredProc.
In this case, I'd recommend using CFQUERY to call your stored procedure,
as
Mike recommended. It works just as well, and you can cache it.
Alternatively, you can cache recordsets from CFSTOREDPROC within the
Session, Application or Server scopes.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
phone: 202-797-5496
fax: 202-797-5444
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
