Having read through the comments on this bug: https://code.djangoproject.com/ticket/22563
I can see that migrations were not originally intended to support changing AUTH_USER_MODEL after the initial migration. However I am confused about whether it now should. The later comments and the documentation imply that swappable models should work provided they have migrations. I got the same error as reported in the bug report, but the workaround was simpler (manually add a dependency on the initial migration for the app containing my custom user model to the migration that added a foreign key to it). Is this a bug that should be reported, or do we live with workarounds? -- 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 [email protected]. To post to this group, send email to [email protected]. 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/87095083-4d2f-4f87-a55c-d98ad083030d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
