#23521: removal of concrete Model from bases doesn't remove it from ModelState
bases
----------------------------+--------------------------------------
Reporter: sir-sigurd | Owner: sir-sigurd
Type: Bug | Status: new
Component: Migrations | Version: 1.7
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by ris):
I invite you all to look at my marked-as-duplicate bug #23818. To me it
seems there is simply no way for django's migration operations to express
a change of {{{bases}}}. {{{parent_link}}}s are created & removed, but the
built-up in-memory representation of the models never understands the new
parentage, meaning certain operations (e.g. in a RunPython operation) will
simply not work right when referring to inherited fields. This goes beyond
{{{makemigrations}}} simply not detecting a change.
--
Ticket URL: <https://code.djangoproject.com/ticket/23521#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.4cc2416a1f99fef6c28c7d84cf59b439%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
