Hi ,

I have an application where I need a pagination, in which

Each user have less than 1000 books on which I need to paginate.

I have several approach in mind , and I would like to know which of
following is better suitable. (order does not matter much)

1) Have a separate counter-index for books for each user and paginate
on it. ( This could be easier but I can't figure out what happen if
any one delete his book , how to rearrange things.. ).

2) Use date based pagination, { I might need to fetch double entity -
and/or two way order to have correct next and previous links. } So ,
Two type of index to maintain.

3) Fetch all the entity and do all the calculation in memory. <-- The
method I find most while googling - and even in devserver too ,
easiest .. what about performance ? -- lots of wastage of data ?

What if user might have more than 1000 books ( future design
upgrade ?? ) .

I also like to know what you guys are doing about pagination?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to