#25100: Document how to avoid ""RuntimeError: Error creating new content types."
when upgrading to 1.8 (skipping 1.7)
--------------------------------------+------------------------------------
Reporter: sachinvettithanam | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.8
Severity: Normal | Resolution:
Keywords: contentype migration | Triage Stage: Accepted
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
* component: Migrations => Documentation
* needs_tests: => 0
* needs_docs: => 0
* type: Bug => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
Please see if https://groups.google.com/d/topic/django-
users/DlRQOdsJL6o/discussion helps. Are you faking the contenttypes
migrations which causes both 0001 and 0002 to be faked? Maybe we could add
a tip about this in the 1.8 release notes since it seems to be a common
issue. `migrate --fake-initial` might resolve that.
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#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/075.2c0014aa666e2080c6a24b81b6e95862%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
