#9519: Add QuerySet.bulk_delete() that issues only a single SQL query
-------------------------------------+-------------------------------------
Reporter: Tarken | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: master
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: database, queryset, | Needs documentation: 0
delete | Patch needs improvement: 0
Has patch: 0 | UI/UX: 0
Needs tests: 0 |
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Comment (by akaariai):
Note that a regular .delete() can avoid the fetching if there are no
cascades, and there are no signals. We currently have no API to ask if
somebody is listening for a signal, but we could easily add one -
pre_delete.has_listeners(`SomeModel`) for example. This way we could
automatically do the right thing in .delete() without need for a new
operation. And, we could optimize deletion of cascades, too.
If there are signals but we want to skip sending those, we could just add
a .delete(signals=False) option for that. I am -1 on ignoring cascades.
This will lead to integrity errors. Or worse, there are DBs which do not
enforce foreign keys.
--
Ticket URL: <https://code.djangoproject.com/ticket/9519#comment:15>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
