From f876c7d08e75d719df5cd34b97cac63fdaae3fcc Mon Sep 17 00:00:00 2001 From: abhiabhi94 <13880786+abhiabhi94@users.noreply.github.com> Date: Fri, 23 Jul 2021 14:13:19 +0530 Subject: [PATCH] Fixed #32957 -- Improved visibility of arguments sections in Model.save() docs. --- docs/ref/models/instances.txt | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index b30ca71142..6cf861638b 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -355,6 +355,10 @@ To save an object back to the database, call ``save()``: .. method:: Model.save(force_insert=False, force_update=False, using=DEFAULT_DB_ALIAS, update_fields=None) +For details on using the ``force_insert`` and ``force_update`` arguments, see +:ref:`ref-models-force-insert`. Details about the ``update_fields`` argument +can be found in the :ref:`ref-models-update-fields` section. + If you want customized saving behavior, you can override this ``save()`` method. See :ref:`overriding-model-methods` for more details. @@ -549,6 +553,8 @@ For more details, see the documentation on :class:`F expressions ` and their :ref:`use in update queries `. +.. _ref-models-update-fields: + Specifying which fields to save -------------------------------