#31326: Deleting a concrete subclass table with no additional fields results
results in invalid migration
----------------------------------+--------------------------------------
Reporter: Stephen Finucane | Owner: nobody
Type: Uncategorized | Status: closed
Component: Uncategorized | Version: 1.11
Severity: Normal | Resolution: invalid
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 Simon Charette):
* status: new => closed
* resolution: => invalid
Comment:
You reported this issue on Django 1.11 but it cannot be reproduced anymore
in Django 2.2+ (likely because of
ad82900ad94ed4bbad050b9993373dafbe66b610).
It can also be easily worked around by removing the `RemoveField`
operation entirely.
Closing this ticket as invalid because the patch won't be backported to
1.11 (it only receives security backport at this point).
--
Ticket URL: <https://code.djangoproject.com/ticket/31326#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.6bd333b44a240eafc62837e67efecfe1%40djangoproject.com.
