I agree with Joshua. That's a very bad experience to force us to go through to migrate. My migration is probably going to be much worse because I have a lot of data, which means that it'll take a very long time (days?) to copy the data across, and by that time the data would have changed on the original app. I cannot bring the app down for extended periods of time while I do this.
Not to mention how much of a hassle it is to change app IDs. I posted an issue here, star it if you agree that this process should be automated: http://code.google.com/p/googleappengine/issues/detail?id=5250 On Wed, Jul 13, 2011 at 6:41 PM, Greg <[email protected]> wrote: > On Jul 13, 1:05 am, Joshua Smith <[email protected]> wrote: > > Frankly, I've never completely groked what an entity group maps to in my > (30+ years of) programming experience. It's certainly not a parent/child > relationship in the usual sense. > > If you figure it out, let me know! I have a app that needs to update > two distinct entity types at the same time. Because they are distinct, > I can't do both in a transaction. Even if it was only one entity type, > I don't want to lock all of them when writing to one, which I believe > is a consequence of making them a group. > > A good article called "entity groups for dummies" seems warranted! > > -- > 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.
