Skip to content
This repository has been archived by the owner on Dec 25, 2023. It is now read-only.

Need clearer distinction between context.map_query and qry_obj.map_async #130

Closed
GoogleCodeExporter opened this issue Jun 10, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

The documentation seems to suggest that they can be used similarly. What is the 
difference and when should each be used? Which should be used for optimum 
performance (as both suggest that they are the "fastest").

Documentation for context.map_query: 
https://docs.google.com/document/d/1rPyB2RmRERAZDPpqy2cxzXeDGyfLhX-s-3dFVpnwFXw/
edit?hl=en_US#heading=h.wniiq5a4ja4o

Documentation for qry_obj.map_async: 
https://docs.google.com/document/d/1rPyB2RmRERAZDPpqy2cxzXeDGyfLhX-s-3dFVpnwFXw/
edit?hl=en_US#heading=h.t1t6424hbp7y

I apologize if this is not the right venue for this question.

Original issue reported on code.google.com by EricHF...@gmail.com on 9 Jan 2012 at 3:30

@GoogleCodeExporter
Copy link
Author

Definitely use qry_obj.map_async(). Context().map_query() is a lower-level API 
that you shouldn't need. Note, that document is way out of date; I have a TODO 
to update it but other things keep getting priority. Fortunately the Google App 
Engine documentation team is helping out with documentation now.

Original comment by guido@google.com on 9 Jan 2012 at 5:16

  • Changed state: WontFix

@GoogleCodeExporter
Copy link
Author

Thank you very much Guido! I will update my corresponding StackOverflow 
question to share the news! I'm looking forward to the documentation, though 
you guys did a great job with the informal documentation!

Original comment by EricHF...@gmail.com on 9 Jan 2012 at 5:19

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant