#29897: Initial migration fails when referencing a custom user model from a
sequence of at least two concrete ancestor models
-------------------------------------+-------------------------------------
Reporter: Steven Ganz | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 2.1
Severity: Normal | Resolution:
Keywords: "custom user model" | Triage Stage: Accepted
"abstract model" "foreign key" |
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:"82353ef940ba661e8c4c1cbc47eb2f62192e4fbe" 82353ef]:
{{{
#!CommitTicketReference repository=""
revision="82353ef940ba661e8c4c1cbc47eb2f62192e4fbe"
Refs #29897 -- Moved autodetector swappable dependency resolution to a
method.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/29897#comment:7>
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.f0ead0c414ec5eddacc7c33f5ffbeef4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
