[4.1.x] Doc'd when pre_save() is called with Model.save()'s update_fields.

Backport of bf47c719719d0e190a99fa2e7f959d5bbb7caf8a from main

1 files changed, 8 insertions, 0 deletions

diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
index 71fb880740..8b2c5b6ef5 100644
--- a/docs/ref/models/instances.txt
+++ b/docs/ref/models/instances.txt
@@ -621,6 +621,14 @@ from the DB will get updated. In effect there is an automatic
 ``update_fields`` in this case. If you assign or change any deferred field
 value, the field will be added to the updated fields.
 
+.. note::
+
+    If ``update_fields`` is passed in, only the
+    :meth:`~django.db.models.Field.pre_save` methods of the ``update_fields``
+    are called. For example, this means that date/time fields with
+    ``auto_now=True`` will not be updated unless they are included in the
+    ``update_fields``.
+
 Deleting objects
 ================