Ajas, if you're using SQL Server 2005 or Oracle, there are much better
solutions...the problem with what you showed in the first link is you (the
server) is always retrieving ALL rows from the given table and pushing those
across the pipe from your SQL server to your web server. There are two
: But if the query
is run *every time* when you go to next page,
inst it: defeating the very purpose
of pagination i.e. less load in performing
query: to get 1000s of records
at once.I think every situation where
you may have 1000s of records being delivered
to CF is potentially suspect.
Architecturally, this may introduce a different approach other than a page
refresh to show the next n-rows.
AJAX, Flex or any event based solution could reduce how and when to get the
next set of records.
I remember in a previous .Net application that there existed a scheme to get
the next set
