#18631: A way to get handle to the generated query for terminal queryset methods
-------------------------------------+-------------------------------------
Reporter: Anssi Kääriäinen | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.4
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* status: new => closed
* resolution: => wontfix
Comment:
I'm not sure this worth keeping around.
Terminal operations such as `update` and `delete` can actually result in
multiple queries (MTI in the case of `update`, chain of `SELECT` and
`DELETE` in the case of `delete` where the `SELECT` must run to return the
actual data that would be passed to `DELETE`) and the cases where you want
to know the exact queries are better served through `django.db` logger
capture or using options such as `--debug-sql` when running tests.
--
Ticket URL: <https://code.djangoproject.com/ticket/18631#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/01070182a486be79-3c2da2d0-d2da-430e-87dc-89586774a164-000000%40eu-central-1.amazonses.com.
