The migrations for mezzanine's apps reside in the source code. Unless you modified mezzanine's models (e.g., with the `EXTRA_MODEL_FIELDS` setting), you wont cause migrations to mezzanine's apps.
On Tue, Jul 19, 2016 at 7:52 AM, Keith Irwin <[email protected]> wrote: > Hopefully this is an easy question for somebody in the loop. > > I seem to have fudged my schemas by creating a new app. It's giving me a > type error, so maybe I forgot to turn off MODELTRANSLATION before executing > makemigrations/migrate. > > I just want to revert to the state I was in before the app existed. > Fortunately, I was smart enough to keep a second copy of my dev.db, which I > restored. > > So I use runserver with the restored dev.db and my project runs fine, data > and all, just like before. However, I get the traditional message "You > have unapplied migrations" > > I run showmigrations and get a neat list of applied and unapplied > migrations. I want to delete all these unapplied migrations, returning > (undoing makemigrations) to the state of the restored db. In my own apps, > I can just delete the unapplied migrations/*.py files. But what about > mezzanine's built-in apps (blog, pages, etc) How do I delete those > migrations. > > In other words, I know how to unapply migrations (manage.py migrate > appname 000#), but how do I unmake the unapplied migrations? > > I haven't found any answers googling, so it's possible that I completely > misunderstand how migrations/dbs work... > > -- > You received this message because you are subscribed to the Google Groups > "Mezzanine Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Mezzanine Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
