Re: [Django] #9363: [feature request] track down where a query is requested for debugging

5 views
Skip to first unread message

Django

unread,
Mar 23, 2014, 4:36:45 PM3/23/14
to django-...@googlegroups.com
#9363: [feature request] track down where a query is requested for debugging
-------------------------------------+-------------------------------------
Reporter: pihentagy | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.0
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: debug , query | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Comment (by claudep):

#22320 was a duplicate with a patch. I think the idea is good, however I'm
a bit worried about the memory consumption, even if production sites
should not be affected. IMO, fixing #12581 is a prerequisite to this one.

--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
Mar 23, 2014, 4:37:31 PM3/23/14
to django-...@googlegroups.com
#9363: [feature request] track down where a query is requested for debugging
-------------------------------------+-------------------------------------
Reporter: pihentagy | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.0
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: debug , query | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------

Comment (by claudep):

Patch for #22320 is
https://github.com/mbox/django/commit/c0a5fa22770b90d3ad0fd24ee80b93bebe03fbec

--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:6>

Django

unread,
Mar 23, 2014, 4:37:43 PM3/23/14
to django-...@googlegroups.com
#9363: [feature request] track down where a query is requested for debugging
-------------------------------------+-------------------------------------
Reporter: pihentagy | Owner: nobody
Type: New feature | Status: new
Component: Database layer | Version: 1.0
(models, ORM) | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: debug , query | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0

Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by claudep):

* has_patch: 0 => 1


--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:7>

Django

unread,
Jun 8, 2014, 4:20:04 PM6/8/14
to django-...@googlegroups.com
#9363: [feature request] track down where a query is requested for debugging
-------------------------------------+-------------------------------------
Reporter: pihentagy | Owner: nobody
Type: New feature | Status: closed

Component: Database layer | Version: 1.0
(models, ORM) | Resolution: wontfix

Severity: Normal | Triage Stage: Accepted
Keywords: debug , query | Needs documentation: 0
Has patch: 1 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 0 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):

* status: new => closed
* resolution: => wontfix


Comment:

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...

--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:8>

Django

unread,
Feb 6, 2015, 11:29:49 AM2/6/15
to django-...@googlegroups.com
#9363: [feature request] track down where a query is requested for debugging
-------------------------------------+-------------------------------------
Reporter: pihentagy | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 1.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: debug , query | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by mbox):

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"

--
Ticket URL: <https://code.djangoproject.com/ticket/9363#comment:9>

Reply all
Reply to author
Forward
0 new messages