#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: closed
Component: Migrations | Version: 1.10
Severity: Normal | Resolution: duplicate
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 Tim Graham):
* status: new => closed
* resolution: => duplicate
Comment:
I think this is a duplicate of #24424 (presumably that ticket will also
verify that the backwards operations also work). If the `RemoveField`
operation is omitted by the autodetector, then this seems to work.
--
Ticket URL: <https://code.djangoproject.com/ticket/27764#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 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.b9f0a6c7e6d87340dda4b095d96d75b2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
