Yes, that is the simplest and the most clean way. As it "freeze" things. However, if the result set is large, this can be a concern(if practical at all). What complicates the matter is the WEB part. Say I have a result set of 1000 rows. That is perfectly all right to store them if we are writing a traditional VB programs as it is usually used by only one user at the client machine(using its memory). But if the app can be potentially used by tens of thousands of people at the same time, that may not be desirable.
Another possible solution I can think of is to have an index on every "front end" sortable column. Then, all it needs is to store the begin/end value of that column and the next select is just a condition of col > last_in_page LIMIT one_pageful. But most DBA would yell and I don't know how to say skip to the n th page. Robert Hicks wrote: > I don't know how he is going to use it but I typically pull everything > out at once and page it. It would be nice to have something that does > this in a db agnostic way. I use Oracle and sometimes it is hard to > find info on paging. > > Robert
