#36657: Make advanced ORM functionality more discoverable
-------------------------------+------------------------------------
Reporter: Lily | Owner: (none)
Type: New feature | Status: new
Component: Documentation | Version: dev
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
-------------------------------+------------------------------------
Changes (by Jacob Walls):
* stage: Unreviewed => Accepted
* type: Uncategorized => New feature
Comment:
I would rather this not become a dumping ground of advanced examples, but
rather a carefully scaffolded journey going from lower to higher
complexity, so that the reader can see that the ORM will be ready to
support them if they ever *do* develop more complex needs.
I'm also envisioning that the ''gathering requirements'' phase here would
involve surfing Trac, Discord, and the forum to collect frequently-asked-
questions around raw SQL usage or ORM help. Maybe about ten or twelve
examples of increasing complexity could be built around the same sample
models.
--
Ticket URL: <https://code.djangoproject.com/ticket/36657#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199d8910d74-1583ff98-8b14-4ead-8d4c-d3dc1c9dcc4d-000000%40eu-central-1.amazonses.com.
