<https://lh5.googleusercontent.com/Z1Za7XqtookiRmFoiGiwwyLypQfFTUcEJHuVdPksBfh-966OT5k8c_t90rnx1qSa0Q=s1600> Ah - I'm using Java and not Python. Appstats does work, and I have set it up on /appstats - this is where I got the write costs in the original post. I guess the /shell is not part of the Java version yet?
At any rate, above image is from doing an IN query filter across numbers 1..10 with none of them returning any results. Each query is run completely separately, and they are not even run concurrently! This means that IN queries are basically useless on AppEngine - why do you even have support for them if they don't work? Are there any plans on the horizon to make 'IN' queries work as in every other nosql database? On Saturday, January 5, 2013 12:49:34 AM UTC+2, Guido van Rossum wrote: > > On Fri, Jan 4, 2013 at 1:59 PM, Ryan Chazen <rya...@gmail.com<javascript:>> > wrote: > > That link - /_ah/stats/shell - does not seem to be working for me on > either > > the dev server or the live server. I get a 404 error. > > Does /_ah/stats work for you? If it doesn't work, you haven't enabled > Appstats in your app.yaml (it's in the builtins section). If that does > work, you must configure the appstats shell in your > appengine_config.py for it to work in production, but it should be on > by default in the dev server. (Python only.) > > -- > --Guido van Rossum (python.org/~guido) > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/KCHGypyDZDIJ. 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.
