#25703: Create topic documentation for Expressions
-------------------------------------+-------------------------------------
Reporter: thatdocslady | Owner:
Type: | thatdocslady
Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jarshwah):
Thinking about this a little more, I think what we should be writing topic
docs on is "Customising the SQL generated by the ORM". Topic name to be
cleaned up.
That's really the entire point of expressions. They let you customise the
query. Lookups and Transforms also help with customising the query. Extra
and Raw, to a lesser extent, also help with this. I think the topic docs
should make this as their focus.
We can then link to Expressions API docs, Lookup/Transform API docs (of
which there is already topic docs on how to create your own and why), with
a light touch on extra/raw.
Thoughts?
--
Ticket URL: <https://code.djangoproject.com/ticket/25703#comment:3>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.f9c63ba7bd6f1562ea0c704eca2eeacf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
