#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: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):
* status: closed => new
* resolution: needsinfo =>
* easy: 0 => 1
Comment:
Steps to reproduce:
1) Have a pre-1.7 project.
2) Upgrade to Django 1.8 (skipping 1.7) and run `manage.py migrate
--fake`.
3) Now, `0002_remove_content_type_name.py` will get fake-applied and the
`name` column in the `django_content_type` table won't be dropped.
We should recommend using `migrate --fake-initial` in the 1.8 release
notes for this case.
--
Ticket URL: <https://code.djangoproject.com/ticket/25100#comment:4>
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.fe5a1870fb2dfe041b2cf19112873887%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
