On Saturday, February 23, 2013 4:59:45 PM UTC-7, GAEfan wrote: > So, let's say I wanted to make a version of Twitter. If I wanted to > search for any tweets in the datastore with a certain #hashtag, that seems > best handled asynchronously. Speed is important there. What to do? >
Running a query asynchronously doesn't make it run faster. It just means that you can do other things in the same request while that query is running. So its really more of question of what other things you need to do in a request. If you really need the features that django non-rel is missing, you could either add them yourself (not the easiest thing to do, but not impossible), or you could skip the django ORM and use the app engine APIs directly. Kinda like writing assembly in a C-based app, you would miss out on some of the fancy django stuff, but sometimes its worth the trade-off. Also, don't forget about all that premature optimization advice. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
