On 2013-08-01, at 11:56 , Nigel Legg wrote: > So is it something I have done wrong?
No. > From what you are saying it has run > the migration No, it has run *part* of the migration, then something failed during the migration. The part that's run is there, what came after the error did not run. > but I am not seeing that - still getting errors when I try to > access the page. If I do manag.py sql myapp I see the schema including the > new fields, but if I go into the shell, import the view, and do > DataTable.objects.all() I get "Unknown column 'myapp_datatable.type2stub' > in 'field list'". > So is there a way to resolve this without deleting the database You can try running the missing part of the migration by hand, and more generally you should take up your question to South's support lists, not Django's. > and > starting again with one that does not have so many issues working with > South? -- 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. For more options, visit https://groups.google.com/groups/opt_out.
