#31416: FieldError when migrating field to new model subclass.
-------------------------------+------------------------------------
Reporter: Eduard Anghel | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
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
-------------------------------+------------------------------------
Changes (by felixxm):
* cc: Markus Holtermann, Simon Charette (added)
* stage: Unreviewed => Accepted
Comment:
Tentatively accepted for a future investigation. I'm not sure if this is
feasible because detecting changes related with models' bases are tricky.
Moreover you will lose data with such change, so IMO it's preferable to
handle this manually.
--
Ticket URL: <https://code.djangoproject.com/ticket/31416#comment:1>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.b179c0124114f97d66ed69cad9bb41c2%40djangoproject.com.
