tickets: 9363
This data as json
| id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 9363 | 2008-10-14 15:13:30 | 2016-10-04 12:03:42 | 2022-03-06 03:44:42.553018 | Accepted | new | Database layer (models, ORM) | New feature | Normal | 1.0 | Add a traceback to each query in CursorDebugWrapper | 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. | nobody | pihentagy | debug , query | 0 | 1 | 1 | 0 | 0 | 0 |