#34796: Deleting child table does not delete rows in parent table when using
multi-
table inheritance
-------------------------------------+-------------------------------------
Reporter: Stephen Finucane | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
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 Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
Comment:
Thanks for the ticket, however migrations doesn't automatically manipulate
(delete/update/add) data. Generated migrations are responsible for
propagating changes in the database structure (DDL). Any changes to this
would be backward incompatible. #21961 is the ticket that must be
implemented (as you already noticed) if you want to tell your db that
related data should be deleted in cascade.
Marking as a duplicate because #21961 will effectively fix this, for users
who opt-in for the cascade behavior.
--
Ticket URL: <https://code.djangoproject.com/ticket/34796#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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018a2c4f9c00-e48b6499-18ad-4b5b-bac8-765d07417f9b-000000%40eu-central-1.amazonses.com.
