Opened 16 years ago
Last modified 8 years ago
#9363 new New feature
Add a traceback to each query in CursorDebugWrapper
Reported by: | Gergely Kontra | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | 1.0 |
Severity: | Normal | Keywords: | debug, query |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Pull Requests: | |||
Description ¶
I'm not a python wizard, so I'm just suspecting the following is possible:
When you examine connection.queries
, it would be great to write out the file and the line, from the Query comes from.
Ok, one must define where the query created (the first time you say filter on a manager, the last time ...), but this should help greatly figuring out why certain queries are executed.
According to the ticket's flags, the next step(s) to move this issue forward are:
- To improve the patch as described in the pull request review comments or on this ticket, then uncheck "Patch needs improvement".
If creating a new pull request, include a link to the pull request in the ticket comment when making that update. The usual format is:
[https://github.com/django/django/pull/#### PR]
.
Change History (10)
comment:1 by , 16 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 14 years ago
Severity: | → Normal |
---|---|
Type: | → New feature |
comment:3 by , 13 years ago
UI/UX: | unset |
---|
comment:5 by , 11 years ago
comment:6 by , 11 years ago
comment:7 by , 11 years ago
Has patch: | set |
---|
comment:8 by , 11 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This feature is provided by the Django Debug Toolbar. It even works for templates. If you need this feature, just install the Debug Toolbar.
I know what the code looks like, and I'd rather leave it up to third-parties...
comment:9 by , 10 years ago
Django debug toolbar doesn't help for any situation where you're not running via a web browser, or in a non-request cycle. So for example, any test case that uses assertNumQueries (see #22320 for example)
The patch for this is a simple few lines, so I don't understand your concern about "what the code looks like"
comment:10 by , 8 years ago
Patch needs improvement: | set |
---|---|
Resolution: | wontfix |
Status: | closed → new |
Summary: | [feature request] track down where a query is requested for debugging → Add a traceback to each query in CursorDebugWrapper |
Aymeric withdraws his wontfix.
PR with a few comments for improvement.
Change UI/UX from NULL to False.