Projects

gae-query-pager

At the present time, the Google App Engine does not provide a built-in pagination support. There are various methods how one can implement limited pagination manually, but writing the paging queries by hand can be tedious and error-prone. Thus this pager tries to alleviate this problem by providing ... [More] an automatic way to generate appropriate paging queries from a base query, and then using these queries to page through the data. The pagination method used is the one described in this document. However the algorithm used was developed from scratch. This pagination method can not be used for a direct jump to a specific page number. Only continuous forward and backward paging using a bookmark and an unique property is supported. Due to the fact that the number of composite indexes allowed on the Google App Engine is limited to 100 per app, it is recommended to optimize your queries to have lower composite index requirements. If you use an ordering on a property and the values of this property are not unique, it is always better to have a copy of this property with these values made unique - that way multiple queries will not have to be used, and the composite index requirements will be much lower. The pager always returns JDO data class instances, however if you use the low-level Java datastore API to efficiently implement optimization techniques using ancestor entities, you can construct a low-level API GaeQuery, and the pager will use that query for paging on the ancestor table, but it will automatically return JDO instances discovered by calling getParent() on the resulting ancestor entities. A GaeQuery instance can be constructed automatically by the pager, using a limited subset of the JDOQL query language, or it can be constructed programatically. GaeQuery is a standalone class that can be easily converted to a JDO API query, or to the low-level API query, including the actual parameter values. To refresh a view to a page, simply reverse the direction and repeat the call. A brief standalone javadocs can be found here. Test pager output can be found here. [Less]

aspnetpager

Outputs page numbers for selecting pages and arrows for previous and next pages. Uses query string variables to determine which page to load based upon the total results given for the result set. Automatically removes arrows and page numbers based upon the currently selected page. Loading the ... [More] user control is very simple. Add the control to the ASPX page and then set the total result count property in the code behind. [Less]