In the instructions posted at the URL: http://code.google.com/p/app-engine-patch/wiki/ReleaseNotes
Is the following comment: Very important: If you upgrade an existing project please set DJANGO_STYLE_MODEL_KIND = False in your settings.py. From now on, the model kind() gets prefixed with the app label, by default, which prevents naming conflicts when multiple apps define models with the same name. Note that Django uses this naming scheme, too, when creating SQL tables. This feature breaks existing models which are stored without the app label, so you need to disable it when upgrading your project (or you can override the kind() method for existing models). On Feb 11, 1:26 pm, "Sharp-Developer.Net" <[email protected]> wrote: > Hi, > > I've updated App Engine Patch from 0.9.3 to 1.0beta and now my app is > broken becouse for some reason models started to be named with a > prefix. > > Like if I had next structure: > > src > - djangoapp > - models.py > Entity > > then before update I had models stored in data store as "Entity". > > Now it's stored & queried (!) as "djangoapp_Entity". > > As a newbie in Python I'm kinda confused where to search for the > change. And not sure is it intentional or a bug. > > This occurs both on dev and PROD :(. > > I do not mind about prefixes in general but I already have a lot of > data in data store and have no idea how to recover to prev state. > > Any comments from App Engine Patch folks would be very welcome. > -- > Alexhttp://sharp-developer.net/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
