#24311: can't syncdb unmigrated custom user on mysql
---------------------------------+--------------------------------------
Reporter: collinanderson | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8alpha1
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 timgraham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
I ran into a similar problem upgrading djangoproject.com to 1.8 because
django-registration doesn't have migrations. My solution was to add
migrations for it. As migrations will become compulsory in 1.9, I believe
expanding
[https://docs.djangoproject.com/en/1.8/topics/migrations/#dependencies the
warning] about having unmigrated apps depend on migrated apps might be
sufficient to address this rather than add more code that's applicable to
1.8 only.
--
Ticket URL: <https://code.djangoproject.com/ticket/24311#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/072.feabd91dd3fe21d48cebda1f4f1e0363%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
