"Hayes, David" wrote:


> Another option: you could cache the query so that the requery on the next
> page will pull the cached version.  This could certainly cause some
> problems; it will not be appropriate in many situations.
> 

I've seen queries go from multiple seconds (huge dataset) down to less
than 20 milliseconds using a cached query. The only time I've ever run
into problem with a cached query is when the user changes the data (via
update or delete). What other problems have you found.

regards,
larry
-- 
Larry C. Lyons
ColdFusion/Web Developer
EBStor.com
8870 Rixlew Lane, Suite 201
Manassas, Virginia 20109-3795
tel: (703) 393-7930 x253
fax: (703) 393-2659
http://www.ebstor.com
http://www.pacel.com
email: [EMAIL PROTECTED]

Chaos, panic, and disorder - my work here is done.
--

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to