#32372: Improve consistency in "Related objects reference" docs.
--------------------------------------+------------------------------------
Reporter: Jack | Owner: Jack
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: 3.1
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Mariusz Felisiak):
* owner: nobody => Jack
* status: new => assigned
* easy: 0 => 1
* stage: Unreviewed => Accepted
Comment:
Examples in this page use reverse relation for a `ForeignKey` not a
`ManyToManyField`, so the be more consistent we could change change the
`Reporter - Article` example to
[https://docs.djangoproject.com/en/3.1/topics/db/queries/#making-queries
Blog - Entry], e.g.:
{{{
class Blog(models.Model):
# ...
pass
class Entry(models.Model):
blog = models.ForeignKey(Entry, on_delete=models.CASCADE)
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/32372#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 unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.79351e09689d6d216120605d6ee1ec6e%40djangoproject.com.
