Permalink
Browse files

Fixed #5068 -- Fixed error in docs/db-api.txt. Thanks, Collin Grady a…

…nd SmileyChris

git-svn-id: http://code.djangoproject.com/svn/django/trunk@6010 bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
adrianholovaty committed Aug 25, 2007
1 parent 861b28f commit b189e266ef1a4f8c3fba39e44e053ec42fc52098
Showing with 15 additions and 5 deletions.
  1. +15 −5 docs/db-api.txt
View
@@ -207,14 +207,24 @@ the database until you explicitly call ``save()``.
The ``save()`` method has no return value.
Updating ``ForeignKey`` fields works exactly the same way; simply assign an
object of the right type to the field in question::
Saving ForeignKey and ManyToManyField fields
--------------------------------------------
Updating ``ForeignKey`` fields works exactly the same way as saving a normal
field; simply assign an object of the right type to the field in question::
cheese_blog = Blog.objects.get(name="Cheddar Talk")
entry.blog = cheese_blog
entry.save()
Updating a ``ManyToManyField`` works a little differently; use the ``add()``
method on the field to add a record to the relation::
joe = Author.objects.create(name="Joe")
entry.author = joe
entry.save()
entry.authors.add(joe)
Django will complain if you try to assign an object of the wrong type.
Django will complain if you try to assign or add an object of the wrong type.
You can find out more about `Queries over related objects`_ below.
How Django knows to UPDATE vs. INSERT
-------------------------------------

0 comments on commit b189e26

Please sign in to comment.