#27617: Better ORM internals documentation
-------------------------------------+-------------------------------------
Reporter: Mads Jensen | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: documentation | Triage Stage: Accepted
internals |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Shai Berger):
* type: Uncategorized => New feature
* component: Database layer (models, ORM) => Documentation
* stage: Unreviewed => Accepted
Comment:
Hi, Thanks for filing this request. I think it is an awesome idea.
There's a simple, "bureaucratic" problem with it: The Django project is
committed to backwards-compatibility with respect to documented features
and behaviors. We don't want that to apply to implementation details,
neither those of the ORM nor otherwise. So we'd need to either create a
"non-committing" section of the documentation (with a different
appearance?), or put this part out of the regular documentation.
--
Ticket URL: <https://code.djangoproject.com/ticket/27617#comment:1>
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/068.88e9772d276deff467cc7cd9c47b44a3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
