#18907: Documentation regarding population of backrefs is incorrect
--------------------------------+------------------------------------
Reporter: simonpercivall | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.4
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 simonpercivall):
When running Django in a larger project, with something like mod_wsgi or
gunicorn instead of runserver, and with Celery or other jobs doing
background processing, models are also not auto-loaded, unless, as you
say, they're loaded as a side-effect of other operations.
Changing the text to say "under normal operation", therefore, is deeply
misleading.
I hesitated whether to submit this as a documentation issue or as a core
bug. It might be argued that population of backrefs is a guarantee that
Django actually ''should'' make. From my perspective, that would probably
be the preferred solution.
--
Ticket URL: <https://code.djangoproject.com/ticket/18907#comment:2>
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 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 https://groups.google.com/groups/opt_out.
