I've not heard of the ability to allow you preserve the app id as far as the datastore is concerned, only the ability to create an alias so it acts like the same app. I wonder if an alias is what Ikai was referring too or if he meant some way to really preserve the app id.
Robert On Wed, Aug 3, 2011 at 20:50, johnP <[email protected]> wrote: > Amen - temporary read-only is fine. The big problem is that my app > makes use of a ton of keys, and in many cases I need to store the keys > as strings (or store keys in pickled blobs). The real chore is to > write scripts to rebuild all the keys after the migration. > > I'm hoping that preserving the app ID will also preserve these > keys... > > please??? > > johnP > > > > > On Aug 3, 1:02 pm, Will Reiher <[email protected]> wrote: >> Ikai, >> >> That's great news! I'm not so worried about a temporary read-only period >> it's the the idea of switching the application id that was scary. I've >> already done it once, and while it was fairly painless, it did affect our >> https requests point to the app-id appspot url. >> >> Thanks for the update - I'm sure many other people will be making the >> switch. > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
