#24299: `migrate auth` throws django.db.utils.IntegrityError
----------------------------+-------------------------------------
Reporter: sir-sigurd | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 1.8alpha1
Severity: Normal | Resolution: fixed
Keywords: 1.8-beta | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"77e3f7dd586908b6c78d9718bbea65846e20e180"]:
{{{
#!CommitTicketReference repository=""
revision="77e3f7dd586908b6c78d9718bbea65846e20e180"
[1.8.x] Fixed #24299 -- Added an auth migration to ensure contenttypes is
migrated.
Without this migration, the auth signal handlers will fail if migrating
only auth.
Backport of 4538cbf17d4391cda22d76bc6ac69f228f7400f2 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24299#comment:9>
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.ca2db9d8112b5c045ed6b9528fd1c1eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
