#24299: `migrate auth` throws django.db.utils.IntegrityError
----------------------------+-------------------------------------
Reporter: sir-sigurd | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8alpha1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+-------------------------------------
Changes (by knbk):
* version: master => 1.8alpha1
Comment:
The removel of `ContentType.name` as a field in
b4ac23290772e0c11379eb2dfb81c750b7052b66 introduced this bug in 1.8.
`ContentType.get_for_model` can't be used at all for non-existing content
types until the `0002_remove_content_type_name` migration is applied.
Making the first migrations of `contrib.auth` and `contrib.admin`
dependant on `0002_remove_content_type_name` solves the issue for those
apps, but not necessarily for all apps that use content types.
--
Ticket URL: <https://code.djangoproject.com/ticket/24299#comment:2>
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/068.722ed8089f6fd71bfe1b8327e815603e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
