I'm using Google App Engine (GAE), the Datastore (using JDO) and doing it in Java.
I want the following to happen:
Let's say I have the following model: Card, it only has one field and it is the time of creation (i call it 'toc').
I want to always retrieve the 3 newest Card-entities when a GET-request is made. Let's say I currently have 5 Card entities in the Datastore called C1, C2 ... C5. They are inserted in that order, meaning C5 are the newest entity.
I now do my GET-request and will thus get the entities: C5, C4 and C3. After I use the entities on the Client-side, lets say 5 minutes later. I want to retrieve the next 3 newest entities. But during those 5 minutes 2 new Cards have been added to the Datastore, it now looks as following: C1, C2, C3, C4, C5, C6, C7.
I now want to actually retrieve C7, C6 and the Card that is the newest but hasn't already been retrieved, meaning I also want C2. i.e. I want C7, C6 and C2.
I've been experimenting with cursors and can't seem to get this behavior. Currently I'm using a query that sorting the Cards ascending, meaning I will get the oldest Cards first and then when I've gone through them all, the Cursor can actually detect when new entries have been added and retrieve them. But if there has been more then 3 added since the last query it will still take the first 3 (instead of the last 3), meaning I will get the 3 oldest Cards of the "new" Cards. Is the any way to get an "end-cursor" without actually getting to the end? If there is I might be able to live with getting the 3 oldest newest Cards.
Real life application: Imagine 9GAG's Fresh category: Newest entries are always on top (easy). BUT in my application the previous ones will most likely never be seen again, meaning I want to avoid repetition. So it should prioritize newest entries and when there is no "new" Cards any more it will continue where you last left off.
Sorry for wall of text! And thanks for any feedback! :)
i will give a work around to get what you want... as you are dealing with real time changes,
- pass the current time (ms) to the query and create a cursor.
- Get the entities which are created before the time you passed.
- save the time (ms) which you passed for the first time in client side, and pass it each time.
- With this you can ignore the entities created after your first request.