summaryrefslogtreecommitdiff
path: root/docs/releases
diff options
context:
space:
mode:
authorAndrei Antoukh <niwi@niwi.be>2012-08-12 22:17:54 +0300
committerAnssi Kääriäinen <akaariai@gmail.com>2012-08-12 22:39:27 +0300
commit99321e30cebbffeafc6ae19f4f92a0a665cbf19b (patch)
tree668b2766ef18a603d18253a12a8e00cfd5dde0c2 /docs/releases
parent59a655988ee95e4b4e4646cebea88b620d8fcdd2 (diff)
Fixed #18306 -- Made deferred models issue update_fields on save
Deferred models now automatically update only the fields which are loaded from the db (with .only() or .defer()). In addition, any field set manually after the load is updated on save.
Diffstat (limited to 'docs/releases')
-rw-r--r--docs/releases/1.5.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/releases/1.5.txt b/docs/releases/1.5.txt
index 4aeb61af94..2896acb36b 100644
--- a/docs/releases/1.5.txt
+++ b/docs/releases/1.5.txt
@@ -42,6 +42,10 @@ keyword argument ``update_fields``. By using this argument it is possible to
save only a select list of model's fields. This can be useful for performance
reasons or when trying to avoid overwriting concurrent changes.
+Deferred instances (those loaded by .only() or .defer()) will automatically
+save just the loaded fields. If any field is set manually after load, that
+field will also get updated on save.
+
See the :meth:`Model.save() <django.db.models.Model.save()>` documentation for
more details.