#31416: FieldError when migrating field to new model subclass.
-------------------------------------+-------------------------------------
Reporter: Eduard Anghel | Owner: Nan Liu
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"114da2d0455594bae0bbda8f2b1d46c5ec854956" 114da2d0]:
{{{
#!CommitTicketReference repository=""
revision="114da2d0455594bae0bbda8f2b1d46c5ec854956"
[3.1.x] Fixed #31416 -- Made autodetector find dependencies for MTI model
creation on base fields removal.
Removing a base field must take place before adding a new inherited
model that has a field with the same name.
Backport of 33c365781abbcc1b21a31b31d95d344a174df0d5 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31416#comment:27>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.553909fb1ab34f80ec800a4af7987cdd%40djangoproject.com.
