#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
I think comment:26 is still very relevant today even if it was made 10
years ago.
All the proposed method `bulk_delete` method does is copy over `delete`
implementation and allow the deletion collector to ignore signals when
determining if the ''fast'' path can be taken so I don't think it warrants
a dedicated method and it feels like the usage of the `bulk_` prefix is
slightly misleading.
Given support for database level `on_delete` is likely to land sooner than
later how relevant would be a `delete(ignore_signals)` flag given the
Pandora box in terms of supporting ignoring signals in all other
interfaces the ORM supports (`Model.save`, `Model.delete`, etc).
--
Ticket URL: <https://code.djangoproject.com/ticket/9519#comment:38>
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/0107018889af2851-a92c4abc-1baa-468d-ab79-450adc4870fb-000000%40eu-central-1.amazonses.com.
