Thanks HLS , I appreciate the quick response. I have already implemented a simple case and its working. I am reading the user guide to make sure that i dont miss anything out.
Josh. On Thu, Feb 24, 2011 at 11:46 PM, Howard Lewis Ship <hls...@gmail.com>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. > > > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
