#32724: Deleting a MTI Child model will leave associated rows in the parent
table.
--------------------------------------------+------------------------
Reporter: Matthias Dellweg | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 3.2
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+------------------------
Steps to reproduce:
1. Create a Parent and a Child model
2. Migrate and populate some rows in the Child table
3. Delete the Child table, create migrations and migrate
4. Observe that the Parent table is not empty
In contrast to that, if you remove rows from the Child table (while
existing), the corresponding rows in the Parent table are deleted too.
This bug happens both on forward as well as reversed migrations.
Sample project:
https://github.com/mdellweg/migrationtest
--
Ticket URL: <https://code.djangoproject.com/ticket/32724>
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/051.f56d2a4dce4855f220af1581c4cd2f5a%40djangoproject.com.
