Also have a look at Tapestry's Hibernate integration [1] which supplies a HibernateGridDataSource [2] that implements pagination and only fetches the necessary objects from the database.
Uli [1] http://tapestry.apache.org/hibernate.html [2] http://tapestry.apache.org/tapestry5.2-dev/apidocs/org/apache/tapestry5/hibernate/HibernateGridDataSource.html On 24.02.2011 21:00, Howard Lewis Ship wrote: > If you look at the source parameter of the Grid, it is a > GridDataSource object. You can bind a List to the source parameter, > and Tapestry takes care of converting the list to a GridDataSource, > but for large result sets from a database, you really want to use the > GridDataSource interface, because it supports sorting and pagination > in the database. > > On Thu, Feb 24, 2011 at 11:53 AM, Josh Kamau <joshnet2...@gmail.com> wrote: >> Hi Users; >> >> How does tapestry do the pagination on a grid? Does it retrieve all the data >> from the database and then does the pagination on the clientside or does it >> retrieve a page at a time from the database? >> >> I have used wicket before and all i did was implement something like >> getIterator(first, count, sortProperty, isAscending), That way, the way the >> data is retrieved is transparent and i can write a dao that gets each page >> at a time without loading all the records. Is there a way to achieve the >> same with tapestry. I mean , is there a way to load a page at a time from >> the database using tapestry pagination. >> >> Kind regards. >> Josh. >> > > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
