summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2013-05-19 11:30:26 -0400
committerTim Graham <timograham@gmail.com>2013-05-19 11:31:27 -0400
commit41bea033b7e6b9d28c99f8c1ddedecad13009bd0 (patch)
treeb116e59ec711e818c34bae61d10552d1361e1cfd
parenta4ab0e8b8648cd4d2dd58396aaccf2be4c23dd85 (diff)
Fixed #20183 - Clarified docs assumption that certain objects exist in database.
Thanks Tomasz Jaskowski for the patch.
-rw-r--r--docs/topics/db/queries.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/topics/db/queries.txt b/docs/topics/db/queries.txt
index a1cb5c79c5..39ef2b33fd 100644
--- a/docs/topics/db/queries.txt
+++ b/docs/topics/db/queries.txt
@@ -102,7 +102,8 @@ Saving ``ForeignKey`` and ``ManyToManyField`` fields
Updating a :class:`~django.db.models.ForeignKey` field works exactly the same
way as saving a normal field -- simply assign an object of the right type to
the field in question. This example updates the ``blog`` attribute of an
-``Entry`` instance ``entry``::
+``Entry`` instance ``entry``, assuming appropriate instances of ``Entry`` and
+``Blog`` are already saved to the database (so we can retrieve them below)::
>>> from blog.models import Entry
>>> entry = Entry.objects.get(pk=1)