Thanks for the response! I got it working again by running manage.py migrate --fake
(when ya can't beat 'em, fake 'em!). I still don't understand though. Before faking, if I ran showmigrations: pages [X] 0001_initial [X] 0002_auto_20141227_0224 [X] 0003_auto_20150527_1555 [X] 0004_auto_20160718_2204 [X] 0005_auto_20160718_2214 [X] 0006_auto_20160719_0018 [X] 0007_auto_20160719_0018 [X] 0008_auto_20160719_0122 [X] 0009_auto_20160719_0124 [X] 0010_auto_20160719_0127 [X] 0011_auto_20160719_0130 [X] 0012_auto_20160719_0149 [ ] 0013_auto_20160719_0205 [ ] 0014_auto_20160719_0702 [ ] 0015_auto_20160719_0806 Pages is a mezzanine app. So where are 0013-0015? They aren't in my 'django_migrations' table because the migrations haven't been applied. For my apps, I can see the myapp/migrations/*.py files for unapplied migrations and delete them. So, if mezz's builtin apps have their migrations wired into the source, does that mean there's a 0013_auto_20160719_0205.py somewhere in my virtualenv folder? I didn't extend/inject any of mezzanine's models, so I wonder why migrations for them are being made at all. On Tuesday, July 19, 2016 at 10:07:12 AM UTC-4, Ryne Everett wrote: > > 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 <hyper...@gmail.com > <javascript:>> 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 mezzanine-use...@googlegroups.com <javascript:>. >> 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 mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
