#27511: Docs incorrect about related_model for GenericRelation being None
-------------------------------------+-------------------------------------
Reporter: Amir Keivan | Owner: nobody
Mohtashami |
Type: Bug | Status: new
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
> Since related_model is set to None for GenericForeignKey it might be
reasonable to set it to None for GenericRelation as well.
`GenericForeignKey.related_model` is set to `None` as it can point to many
models by the generic nature of the foreign key. `GenericRelation` always
point to a single reverse model so I believe things should be kept this
way.
--
Ticket URL: <https://code.djangoproject.com/ticket/27511#comment:5>
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/070.94e54f6e8b51e38f51077fefc053df33%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
