@Stephen Wow! I'm grateful to you for taking time out to make things so clear. From what I see, you're suggesting to have a different key that when present indicates a tweet as 'Read'.
You're right, there would be pagination so I'll be displaying say 50 tweets per page. Now, I would fetch 50 tweets and then check if any of the tweets have a key in the 'Read' table. Suppose it has, then my pagination would go for a toss. I hope you're getting me? Pagination becomes cumbersome if I try to match an entity's status in a different table :( -N -- 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.
