We're upgrading an app from django 1.4 step-by-step through all the versions at least to 1.8. Got a self-inflicted problem with the new migrations in 1.7.
Before we went to 1.7, we added a new field to a model, and migrated the db using South. Then when we went to 1.7, we restarted all the migrations. Unfortunately, we had one database that did not get the South migration with the new field. When we merge in the new code with the new field and try a migrate on the unmigrated database, it does nothing. I suppose because all we got now is the new-in-1.7 initial migration. And of course when I try to run the new code against the unmigrated db, I get an error about the missing field. I know we did wrong to leave that db unmigrated. But do we have any options for recovery now? Other than dump the data, recreate the db, and reload? -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3b316785-23c0-4d49-9150-49da28d301ac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
