#29940: Update "Performing raw SQL queries" doc in 2.1 to recommend not using
raw()
------------------------------------------------+------------------------
Reporter: Katie McLaughlin | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 2.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
The documentation on this page is 5-10 years old and doesn't reflect the
current state of the ORM, where there shouldn't be a reason to drop to
raw() SQL any more, given annotations, aggregation, explain plans and
custom query expressions.
It should be updated to have above the fold: "Don't do this". But until
`raw()` is completely removed, the page should detail how to do it.
I'll submit a PR to do just this, but I would appreciate a second opinion
on how best to word/present this.
https://docs.djangoproject.com/en/2.1/topics/db/sql/
Reference talk: https://youtu.be/p9Bgr5VOISo?t=1433
--
Ticket URL: <https://code.djangoproject.com/ticket/29940>
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/049.7868203a8a93fcdd3ebb61460f7dbcef%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
