#25092: Inconsistency in Query.__str__ and actual query
-------------------------------------+-------------------------------------
Reporter: coldmind | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by coldmind):
Well, I can investigate if it is feasible.
The point about "a basic representation of the query" seems strange for
me. Why should we have a tool that differs from reality?
The practical thing is to have ability to get actual query without looking
to logs.
--
Ticket URL: <https://code.djangoproject.com/ticket/25092#comment:2>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.1a0691a98df0ff04e651f93226cb3ecb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
