diff options
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/instances.txt | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index f0306a7460..f9f11cac0d 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -132,6 +132,9 @@ value from the database:: >>> obj.field # Loads the field from the database .. method:: Model.refresh_from_db(using=None, fields=None) +.. method:: Model.arefresh_from_db(using=None, fields=None) + +*Asynchronous version*: ``arefresh_from_db()`` If you need to reload a model's values from the database, you can use the ``refresh_from_db()`` method. When this method is called without arguments the @@ -188,6 +191,10 @@ all of the instance's fields when a deferred field is reloaded:: A helper method that returns a set containing the attribute names of all those fields that are currently deferred for this model. +.. versionchanged:: 4.2 + + ``arefresh_from_db()`` method was added. + .. _validating-objects: Validating objects @@ -406,6 +413,9 @@ Saving objects 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) +.. method:: Model.asave(force_insert=False, force_update=False, using=DEFAULT_DB_ALIAS, update_fields=None) + +*Asynchronous version*: ``asave()`` For details on using the ``force_insert`` and ``force_update`` arguments, see :ref:`ref-models-force-insert`. Details about the ``update_fields`` argument @@ -416,6 +426,10 @@ method. See :ref:`overriding-model-methods` for more details. The model save process also has some subtleties; see the sections below. +.. versionchanged:: 4.2 + + ``asave()`` method was added. + Auto-incrementing primary keys ------------------------------ @@ -644,6 +658,9 @@ Deleting objects ================ .. method:: Model.delete(using=DEFAULT_DB_ALIAS, keep_parents=False) +.. method:: Model.adelete(using=DEFAULT_DB_ALIAS, keep_parents=False) + +*Asynchronous version*: ``adelete()`` Issues an SQL ``DELETE`` for the object. This only deletes the object in the database; the Python instance will still exist and will still have data in @@ -660,6 +677,10 @@ Sometimes with :ref:`multi-table inheritance <multi-table-inheritance>` you may want to delete only a child model's data. Specifying ``keep_parents=True`` will keep the parent model's data. +.. versionchanged:: 4.2 + + ``adelete()`` method was added. + Pickling objects ================ |