summaryrefslogtreecommitdiff
path: root/docs/ref/models
diff options
context:
space:
mode:
Diffstat (limited to 'docs/ref/models')
-rw-r--r--docs/ref/models/expressions.txt11
1 files changed, 4 insertions, 7 deletions
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt
index daf8440512..91786b3622 100644
--- a/docs/ref/models/expressions.txt
+++ b/docs/ref/models/expressions.txt
@@ -119,14 +119,11 @@ know about it - it is dealt with entirely by the database. All Python does,
through Django's ``F()`` class, is create the SQL syntax to refer to the field
and describe the operation.
-.. note::
-
- In order to access the new value that has been saved in this way, the object
- will need to be reloaded::
+To access the new value saved this way, the object must be reloaded::
- reporter = Reporters.objects.get(pk=reporter.pk)
- # Or, more succinctly:
- reporter.refresh_from_db()
+ reporter = Reporters.objects.get(pk=reporter.pk)
+ # Or, more succinctly:
+ reporter.refresh_from_db()
As well as being used in operations on single instances as above, ``F()`` can
be used on ``QuerySets`` of object instances, with ``update()``. This reduces