mirror of
https://github.com/django/django.git
synced 2025-03-06 15:32:33 +00:00
[4.2.x] Fixed #34242 -- Doc'd that primary key is set to None when deleting objects.
Backport of 5cd1385356d4b275133ddb0f8c78b2f37c5901eb from main
This commit is contained in:
parent
84927e110e
commit
fa52bb7774
@ -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``
|
||||
----------
|
||||
|
||||
|
@ -664,8 +664,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`.
|
||||
|
Loading…
x
Reference in New Issue
Block a user