Hi ten_foot_ninja, We had a similar problem in our application. To resolve it, we reworked things to use calculable key_names for entities. This way, if you know the key_names in advance, you can fetch all the entities in parallel using db.get_by_key_names(). I wrote a detailed snippet about this in this thread: http://groups.google.com/group/google-appengine/browse_thread/thread/57080456fe9a23ec/f31bd790e7954ac5#f31bd790e7954ac5
Cheers! On Sep 23, 1:30 am, ten_foot_ninja <[email protected]> wrote: > Hello, > Right now, I can only have 30 items in an IN or != sub query. > > Also, I understand that these sub queries are done in sequence so > there isn't any performance difference between using IN and just > looping over an array of keys and fetching each record using the key > in the current iteration. > > Does Google plan on running IN and != queries asyncronously any time > soon to boost performance? > Also, are there any plans to loose the (rather lame) 30 sub query > limit? > > Thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
