Fixed #34242 -- Doc'd that primary key is set to None when deleting o…

…bjects.
nikita51bot · Jan 20, 2023 · 5cd1385 · 5cd1385
1 parent cc8aa6b
commit 5cd1385
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 2 deletions.
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
@@ -457,6 +457,9 @@ The primary key field is read-only. If you change the value of the primary
 key on an existing object and then save it, a new object will be created
 alongside the old one.
 
+The primary key field is set to ``None`` when
+:meth:`deleting <django.db.models.Model.delete>` an object.
+
 ``unique``
 ----------
 

diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
@@ -644,8 +644,9 @@ Deleting objects
 
 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
-its fields. This method returns the number of objects deleted and a dictionary
-with the number of deletions per object type.
+its fields, except for the primary key set to ``None``. This method returns the
+number of objects deleted and a dictionary with the number of deletions per
+object type.
 
 For more details, including how to delete objects in bulk, see
 :ref:`topics-db-queries-delete`.