Hi PK, The dev~ prefix is there to more closely replicate what happens for many apps running on the App Engine servers: they have a s~ in the APPLICATION_ID environment variable. (Specifically, the ones running on the High Replication Datastore). This will help developers identify where they're relying on it. You should use the new (and possibly not yet included in our docs--if not, it will be soon) app_identity API.
from google.appengine.api import app_identity appid = app_identity.get_application_id() Is this what is causing you issues? As a workaround (or if you want to simulate the behavior of the Master/ Slave datastore), you can use --default_partition="" on the command line, but you should move your application to use the API method. Also note that if you have existing information in your dev appserver datastore, it will "appear" to have flushed when the full appid changes (from appid to dev~appid); you can use the flag to keep it as before, or use the bulkloader to dump/restore across app ids. --Matthew On Jul 13, 1:06 am, PK <p...@gae123.com> wrote: > A lot of great long expected features. Thanks!! > > I just started to experiment and the dev~ prefix is breaking scripts and > processes I have been using. What motivated this change? > > Thanks > PK -- 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.
