#14091: Fix incorrect quoting in connection.queries
-------------------------------------+-------------------------------------
Reporter: danielr | Owner:
Type: Bug | Status: new
Milestone: | Component: Database layer
Version: 1.2 | (models, ORM)
Resolution: | Severity: Normal
Triage Stage: Accepted | Keywords:
Needs documentation: 0 | Has patch: 1
Patch needs improvement: 0 | Needs tests: 0
| Easy pickings: 0
-------------------------------------+-------------------------------------
Comment (by aaugustin):
Alex, the reasons for fixing this are:
- make it possible to test queries by copy-pasting from the debug bar or a
debug log. That is useful to troubleshoot performance issues: `./manage
dbshell` then `EXPLAIN <<Ctrl-V>>`. Re-quoting manually complex queries
is just a pain. The framework should do that for us.
- remove a common source of questions and frustration for users, as seen
on #django and in duplicate tickets.
Also, Django is supposed be a framework for perfectionnists; IMHO the
status quo ''yeah, it's buggy, but we say it in the small print...''
doesn't live up to this goal. Should we ask django-developers for other
opinions?
--
Ticket URL: <http://code.djangoproject.com/ticket/14091#comment:10>
Django <http://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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
