Thanks for your quick reply.
I just simply used the <t:dataTable> and added scroller below the data table. It is sorting on all records. It is putting entire list into table in the session. Then the subsequence walking between pages is very fast.
Hmm, it seems I need a better way to handle this. Since all data were pull in the backing bean within the session scope. Then if I only put, for example 25 rows as the first page of the dataTable but for the scroller, I need it to show all pages, whenever I click the next page, I just go to the session and get whatever I need instead of going back DB. Will this work?
Thanks for any enlightments:-)
Emily
On 2/6/06, Dave <[EMAIL PROTECTED]> wrote:
how would you apply sorting by cliking a column? Sorting the whole result set? or just the current page? or query the DB again order by that column?Thanks!
Werner Punz <[EMAIL PROTECTED]> wrote:Emily Gu schrieb:
> Hi,
>
> I have a page that used , it only shows 5 on the each page.
> With total 7950 as returned data, it is 1590 pages. But it took 1.5
> minutes to show up the first page that only has 5 rows. I checked the
> query, it only took 240 msecs.
>
> Please let me know if you have any better idea in speeding up the page
> loading but still apply all sorting, paginating mechanism as what
> provides.
>
Yes... you probably loaded the entire list into the table, there is no
need for doing that, there is a generic datamodel interface/class
underneath of all things, by implementing your own datamodel
you can achieve pagination and only have to load one page per time.
That way I managed tables of 15.000 rows and more without any
significant performance impact.
But beware, implementing a datamodel is not what I would call a walk in
the park.
Relax. Yahoo! Mail virus scanning helps detect nasty viruses!
