diff options
| author | sarahboyce <sarahvboyce95@gmail.com> | 2022-09-23 23:13:46 +0200 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2022-09-27 13:46:44 +0200 |
| commit | bf47c719719d0e190a99fa2e7f959d5bbb7caf8a (patch) | |
| tree | 7e05c7276a77684f02f42070b923cab6a0f05753 | |
| parent | ae3d575ec3873d87d187783ea706a868aefc33b6 (diff) | |
Doc'd when pre_save() is called with Model.save()'s update_fields.
| -rw-r--r-- | docs/ref/models/instances.txt | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index 5ae34b9a77..7fc4465afa 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 ================ |