If you upload a new major version, it doesn't become the default version until you switch to it. There's no need to test with a different application id (well, unless you expect to be writing code so bad it breaks your production data horribly.)
On Jun 17, 9:25 am, NealWalters <nealwalt...@nealwalters.com> wrote: > > I would suggest using version control if you want to be able to easily > > revert,... > > I'm using Mercurial, so I have that. I think my point is that when > you upload a new version of an app, you really have no idea if it's > going to work or not. So your site could be down while you are trying > to upload a previous version. If I understand correctly, the the > version number, I can just click a checkbox on the admin console and > go back to a prior version within seconds. > > I think the best practice would be to create a second Google App, then > upload the code there, test the application, then re-upload to the > main site. Any opinions on that? > > I assume each application has an entire separately database correct? > (Isn't the app name part of the keys to all the entities?) > > >Google Apps do not provide support for App Engine. > > So what is the official support path for App Engine? Why did the > error I got have a link to Google/Apps support? If I open a ticket > with them, would they a least email me back with a message that says > they don't support something? > > Thanks, > Neal Walters --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
