#9519: Add QuerySet.bulk_delete() that issues only a single SQL query
-------------------------------------+-------------------------------------
Reporter: Joey Wilhelm | Owner: Akash
| Kumar Sen
Type: New feature | Status: assigned
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: database, queryset, | Triage Stage: Accepted
delete |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Akash Kumar Sen):
After some research I would like to amend my earlier proposition to the
following:
- It does not make sense to delete an object only, ignoring the related
models.
- The current deletion already takes care of the deletion in constant
number of queries for cascading relations.
- So if we can just ignore the signals and perform fast deletion of the
models those have pre/post save signals on deletion that will be enough.
Let me know if there is any possible flaws in my proposition.
--
Ticket URL: <https://code.djangoproject.com/ticket/9519#comment:35>
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/010701887551235b-0b20909e-e94f-4a22-8647-8cf1c2d1aa85-000000%40eu-central-1.amazonses.com.
