#27746: Database migration fail when removing a child model containing only
foreignkeys in a multi-table inheritance context on MySQL
-------------------------------------+-------------------------------------
Reporter: David CHANIAL | Owner: nobody
Type: Bug | Status: new
Component: Database layer | Version: master
(models, ORM) |
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 Simon Charette):
* status: closed => new
* version: 1.9 => master
* resolution: duplicate =>
* stage: Unreviewed => Accepted
Comment:
Tim, I re-opened the ticket because I would expect the auto-detector to
generate a single `migrations.DeleteModel` in this case.
#24424 is related in the sense that making sure that altered tables always
have a column would prevent the reported crash but issuing a `DROP COLUMN`
for every single fields a model has to finally `DROP` the table doesn't
make much sense.
--
Ticket URL: <https://code.djangoproject.com/ticket/27746#comment:2>
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.0cac5979a412c4cbe759f87271936386%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
