From 4cf8913faea15bcaf21ef78679c1d2c39fd0fbff Mon Sep 17 00:00:00 2001 From: GappleBee Date: Sat, 24 Aug 2024 11:51:20 +0100 Subject: [PATCH] Clarified what a ForeignKey relationship entails in documentation. --- docs/intro/tutorial02.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/intro/tutorial02.txt b/docs/intro/tutorial02.txt index d43c82c5d2..441fb0a209 100644 --- a/docs/intro/tutorial02.txt +++ b/docs/intro/tutorial02.txt @@ -154,9 +154,9 @@ A :class:`~django.db.models.Field` can also have various optional arguments; in this case, we've set the :attr:`~django.db.models.Field.default` value of ``votes`` to 0. -Finally, note a relationship is defined, using -:class:`~django.db.models.ForeignKey`. That tells Django each ``Choice`` is -related to a single ``Question``. Django supports all the common database +Finally, note that a relationship is defined, using +:class:`~django.db.models.ForeignKey`. That tells Django that each ``Choice`` is +related to a single ``Question``. However, this doesn't mean that each ``Question`` is related to only one ``Choice``. One ``Question`` could have many ``Choice`` instances related to it. As a result, this relationship would be defined as many-to-one. Django supports all the common database relationships: many-to-one, many-to-many, and one-to-one. Activating models