#27764: Running migration that deletes child model (in multi-table inheritance)
backwards results in an error
-------------------------------------+-------------------------------------
Reporter: Alexandru | Owner: nobody
Mărășteanu |
Type: Bug | Status: new
Component: Migrations | Version: 1.10
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 Alexandru Mărășteanu):
* status: closed => new
* resolution: duplicate =>
Comment:
I don't think it's related to #24424 My guess is the operations
`[RemoveField, DeleteModel]`, when run in reverse, will generate
`[CreateModel, AddField]` so what happens is the `AddField` there is
redundant, hence the error. Again, the error appears not when you run the
migration forward (i.e. to delete the model), but when you run it backward
(i.e. to re-create the model).
--
Ticket URL: <https://code.djangoproject.com/ticket/27764#comment:4>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.e39d31d6b8ec0c38a2682a0cf48b8e14%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
