Re: Is 1.7 RC1 supposed to support migrations changing user model? Not sure whether to report error as bug!

Report it. Migrations is a new feature and it is better to report any encountered issues now before it is released.

Regards,
Michael Manfre

On Wednesday, July 9, 2014 3:10:26 AM UTC-4, graeme wrote:
Having read through the comments on this bug:


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 django-users+unsubscribe@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/282129d7-1ff3-4522-a157-8d1f6730ee99%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.