My guess is that the ListProperty does have a maximum. Even if it didn't, you'll eventually hit the maximum storage for a single entity.
So, if you really need it to scale further, you should put the ids in the datastore separately. Or, if your application can tollerate it, you could combine these two approaches. Fill a list up to a certain amount, and then create a new entity when the list gets full. What do these thousands of ids represent? Do you just need to put and get all of them at once, or are there more complicated things you need to do? -- Kyle Mulka Co-Founder, DealSavant http://www.dealsavant.com On Apr 19, 2:15 am, nischalshetty <[email protected]> wrote: > Every user in my app would have thousands of ids corresponding to them. I > would need to look up these ids often. > > Two things I could think of: > > 1. Put them into Lists - (drawback is that lists have a maximum capacity of > 5000(hope I'm right here) and I have users who would need to save more than > 150,000 ids) > 2. Insert each id as a unique record in the datastore (too much of data? as > it would be user * ids of all users). Can I batch put 5000 records at a > time? Can I batch get at least 100 - 500 records at a time? > > Is there any other way to do this? I hope my question's clear. Your > suggestions are greatly appreciated. -- 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.
