#30527: Problem with creating migrations for subclassed field changes.
-------------------------------+--------------------------------------
Reporter: Wolfgang Fehr | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Changes (by Wolfgang Fehr):
* status: closed => new
* resolution: invalid =>
Comment:
I tried out `deconstruct()`, but still had the same problem. (also see
[https://stackoverflow.com/questions/56422003/no-new-migration-for-
subclass-of-subclass-of-a-field Stackoverflow])
(also tried `deconstruct()` in the parent-field)
--
Ticket URL: <https://code.djangoproject.com/ticket/30527#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 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/063.746043eaec5ee0d83d091fcce06313fc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
