Thanks, that would be my inclination as well, however, this would be on a Load Balanced environment, which is not sharing Session Variables (ala J2EE), and is using non-sticky content switch sessions, meaning the user could find themselves on another box while data may change resulting in inconsistency.
- Calvin
----- Original Message -----
From: Dave Watts
To: CF-Talk
Sent: Monday, December 22, 2003 8:39 AM
Subject: RE: SQL Server 2000 and Pagination
> I'm curious how folks are implementing pagination using SQL
> Server 2000 and avoiding returning entire recordsets to CF.
>
> In other words, if I have a search result set of 1,000 rows,
> and the user will be walking through that recordset 25 rows
> at a time using <prev> <pagenumbers> <next> methods, how are
> folks limiting the result set to only the current 25 rows
> needed to display.
I don't know what most people are doing, but I'd generally recommend that
you cache the recordset in CF using either CACHEDWITHIN or CACHEDAFTER
attributes of CFQUERY, or by storing it in a persistent scope (Session,
Application, Server). There's nothing specific to SQL Server about that, of
course.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
