#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
-------------------------------+------------------------------------
Comment (by Adam (Chainz) Johnson):
> Maybe the makemigrations could present some kind of info about the data
being lost and let the user decide if the migrations be applied or not?
Yes, or it could at least detect that the migration it generates can't be
applied without manual editing to control the data loss, and it could show
a warning/message about this.
--
Ticket URL: <https://code.djangoproject.com/ticket/31416#comment:3>
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.1dd7535b9f5ead1a143323b824c315ec%40djangoproject.com.
