In South, automatically generated migrations that add models fire the function send_create_signal(), which among other things, results in a ContentType record being written for the new model. Except that it doesn't, because it actually just queues up that signal to be fired at the end of the whole process by the function really_send_create_signal().
This is trouble for subsequent data migrations that are counting on those ContentType records. To date I've had to manually changesend_create_signal() to really_send_create_signal() to immediately fire that action and set up future data migrations correctly. Obviously, that is an ugly process. My question is: In Django 1.7, where Migrations replaces the need for South, how will this function? -- 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/391140eb-ee96-4b1a-b833-df38608cb527%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
