I don't know what you mean about "running a loop" of filter calls, but something like Class.all().filter().filter()... is very efficient. My impression is that the GQL interpretation is slightly more expensive, but that the difference is negligible.
Note that the call to the data store does not occur until you actually issue the fetch or get ... and this is what's really expensive. On Mar 5, 4:44 pm, pedepy <paul.ro...@gmail.com> wrote: > is there any difference in performance to use a single query call > (like in, "WHERE prop = value AND prop = value, etc" vs running a loop > of filter() calls and then executing the query ? > > seems to me that if you can build your query all in one shot, you can > avoid one or many loop(s) in your code ... but everyone seems to be > all about using all().filter() these days .. > > help? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
