There is probably some way to integrate the statistics API into a general
purpose paging library, but I don't think it's necessary. Perhaps this could
be useful to determine how many "pages" of data are available, but if you're
using the paging techniques described in
http://code.google.com/appengine/articles/paging.html, you only need to be
able to know if there are more results remaining, which you can do by
fetching one more than needed.
- Jason
On Tue, Oct 20, 2009 at 4:47 AM, robinc wrote:
>
> Could the new Datastore Stats API be used for paging? To return
> information about numbers of entities in the datastore?
>
> Or is it not really meant to be used for this?
>
> Apart from anything else, I can't get statistics to work, but that's a
> separate problem...
>
> On Oct 8, 8:29 pm, Mouseclicker wrote:
> > Hearing that cursoring is being supported in one of the next releases
> > is excellent news! Thanks for this update.
> > However one decision that I really do not understand: Why is the
> > bigtable timestamp not exposed in the Java API?
> >
> > One way to limit query results and to exactly page through the result
> > set would be based on time stamps. This information would be available
> > in the store but cannot be accessed in the Java API. It would be
> > useful for other use cases as well, e.g. detect concurrent
> > modifications of an entity. Why do I have to duplicate this
> > information in my own property which would be available from the
> > system.
> >
> > Can anyone tell why Google made that decision?
> >
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-java@googlegroups.com
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en
-~--~~~~--~~--~--~---
