#22518: Migrations broken with custom user model
---------------------------------+--------------------------------------
Reporter: melinath | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7-beta-2
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+--------------------------------------
Changes (by melinath):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Interesting to note is that contenttypes *is migrated*, so this *should*
work. My guess is that the migration isn't including the contenttypes app
in the fake ORM, because it doesn't expect to need them. The first
migration that's failing is the one where the custom user model is
introduced. (All subsequent migrations also fail with this error if you
get to them by using an older django commit.)
--
Ticket URL: <https://code.djangoproject.com/ticket/22518#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.dd88d1ff5a1f5c5da7a5e16955b68aea%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
