If you're going for pulling it fresh from the DB on every hit, you've got at least couple good options.
1) cache it in ColdFusion - just use the cachedWithin attribute of cfquery, it's easy, it works great. Set it to a day or 5 minutes or 1 minute or even 10 seconds if you're concerned about the data being out of date. This is generally good practice anyway, to prevent cheap DoS hack attempts - you know, the one where you just hold down the F5 key on your competitor's site to tick them off. 2) Cache it in the browser - paginate them with javascript. Slow load time, fast interaction once loaded. And remember, for server-side paging (next/prev buttons, etc), you should use my CFC - http://paginationcfc.riaforge.org/ nathan strutz [Blog and Family @ http://www.dopefly.com/] [AZCFUG Manager @ http://www.azcfug.org/] On Wed, Feb 18, 2009 at 12:48 PM, Mike Soultanian <[email protected]>wrote: > > If I have a table with 60,000 records - should I use query caching for > the next/prev browsing, or should I pull the next/prev page of records > every time the user presses the next/prev buttons? I'm leaning towards > the latter as it just seems to make more sense memory-wise. > > Thanks, > Mike > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;207172674;29440083;f Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:319506 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
