Hi, I'm afraid I don't have them. Apparently after deleting my database file and then just running manage.py makemigrations, it deleted the old migration files and started anew. Right now I'm also unable to re-produce it on purpose :( But it happened a couple of times for me since I regularly make multiple changes to my model (I'm still at the beginning of development) but if I just add a single new field now it works as expected.
Maybe sometimes Django can't detect changes to my file because I store my project in my dropbox folder and maybe this might be messing it up? On Monday, December 8, 2014 1:04:37 PM UTC+1, Markus Holtermann wrote: > > I tried to reproduce the problem with the steps you explained, but it > works fine for me. Can you post your existing migration files for that app > too, please. This will then hopefully give us some hints to solve your > problem. > > -- 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 http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/530b0a83-e651-45b7-9b39-1169acc0a979%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
