mirror of
https://github.com/django/django.git
synced 2025-03-25 16:50:45 +00:00
[1.5.X] Fixed #20183 - Clarified docs assumption that certain objects exist in database.
Thanks Tomasz Jaskowski for the patch. Backport of 41bea033b7 from master
This commit is contained in:
parent
694f4ff9e2
commit
66005c643c
@ -100,7 +100,8 @@ Saving ``ForeignKey`` and ``ManyToManyField`` fields
|
|||||||
Updating a :class:`~django.db.models.ForeignKey` field works exactly the same
|
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
|
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
|
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
|
>>> from blog.models import Entry
|
||||||
>>> entry = Entry.objects.get(pk=1)
|
>>> entry = Entry.objects.get(pk=1)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user