@Tim That seems like a new approach that I did not have in mind. I can put them into an unindexed text field. I however do need to search for a bunch of ids to see if they are present in the datastore for a given user. Using the unindexed approach, I would need to pull all the ids in memory and then search over them.
Seems good but I've seen when you have hundreds of thousands of ids, the 1 mb limit is breached. So if I'm not wrong, I would still need to have multiple rows when the user has more than a certain number of ids. As far as serializing and de-serializing costs are involved, in Brett Slatkin's Google IO talk ( http://goo.gl/1KVvX see page 21) he mentions that serialization overhead is something that is best avoided though I wouldn't mind it so much if it solves my purpose. My priority would be to find a datastore approach to solve my problem (of querying to check is a list of 100 ids are present for a particular user). If I'm not able to then I would probably go with the approach that you have mentioned. -- 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.
