Databases
StackOverflow2013
Postsdbo
POdevappserver2, remote_api, and --default_partition
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POdevappserver2, remote_api, and --default_partition
    text
    copied!<p>To access a remote datastore locally using the original dev_appserver I would set --default_partition=s as mentioned <a href="https://stackoverflow.com/questions/9280613/badrequesterror-app-smyapphr-cannot-access-app-devmyapphrs-data-why/9281772#9281772">here</a></p> <p>In March 2013 Google made devappserver2 the default development server, and it does not support --default_partition resulting in the original, dreaded:</p> <pre><code>BadRequestError: app s~appname cannot access app dev~appname's data </code></pre> <p>It appears like the first few requests are served correctly with </p> <pre><code>os.environ["APPLICATION_ID"] == 's~appname' </code></pre> <p>Then a subsequent request results in a call to /_ah/warmup and then</p> <pre><code>os.environ["APPLICATION_ID"] == 'dev~appname' </code></pre> <p>The docs specifically mention related topics but appear geared to dev_appserver <a href="https://developers.google.com/appengine/docs/python/tools/devserver" rel="nofollow noreferrer">here</a></p> <blockquote> <p>Warning! Do not get the App ID from the environment variable. The development server simulates the production App Engine service. One way in which it does this is to prepend a string (dev~) to the APPLICATION_ID environment variable, which is similar to the string prepended in production for applications using the High Replication Datastore. You can modify this behavior with the --default_partition flag, choosing a value of "" to match the master-slave option in production. Google recommends always getting the application ID using the get_application_id() method, and never using the APPLICATION_ID environment variable.</p> </blockquote>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload