Another idea for saving query times for "N" next records is to store the
query as a session variable and you don't even have to run that query file
at all.
<cfset session.savedquery = queryname>
then you can do your <cfoutput query="session.savedquery" maxrows="#nrows#">
be sure to put <cflock> around your <cfset> when setting session vars.
-Craig
-----Original Message-----
From: Kola Oyedeji [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 08, 2001 5:53 AM
To: CF-Talk
Subject: using WDDX for next 'n' style browsing
I am passing a query object which consists of 1000 records in a hidden form
field between pages as a
WDDX packet, are there any reasons why this is a bad idea, such as limits to
the amount of data which can be held in a form field or passed in a form?
The reason for this is to save a trip to the server for each page of result.
Are there any better solutions, would cacheing the query and executing it
again for every page be more efficient than trying to offload the processing
onto the client's machine?
Thanks
Kola
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
