Browse files

Fixed #10303 -- Corrected a contradiction in the docs regarding the c…

…apabilities of the .update() clause that was introduced by the documentation for F() expressions. Thanks to gluckj for the report.

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent fc02370 commit 322a6a9d1dffee284bb9ea1b309e64f7fa7411b5 @freakboy3742 freakboy3742 committed Feb 19, 2009
Showing with 3 additions and 3 deletions.
  1. +3 −3 docs/topics/db/queries.txt
@@ -767,9 +767,7 @@ a ``QuerySet``. You can do this with the ``update()`` method. For example::
Entry.objects.filter(pub_date__year=2007).update(headline='Everything is the same')
You can only set non-relation fields and ``ForeignKey`` fields using this
-method, and the value you set the field to must be a hard-coded Python value
-(i.e., you can't set a field to be equal to some other field at the moment).
+method. To update a non-relation field, provide the new value as a constant.
To update ``ForeignKey`` fields, set the new value to be the new model
instance you want to point to. Example::
@@ -795,6 +793,8 @@ Just loop over them and call ``save()``::
for item in my_queryset:
+.. versionadded:: 1.1
Calls to update can also use :ref:`F() objects <query-expressions>` to update
one field based on the value of another field in the model. This is especially
useful for incrementing counters based upon their current value. For example, to

0 comments on commit 322a6a9

Please sign in to comment.