diff options
| author | noFFENSE <orazkhanmansur@gmail.com> | 2023-01-18 16:56:24 +0600 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-01-20 10:57:30 +0100 |
| commit | fa52bb77747be33dc9dfb07c26307e60958adaaa (patch) | |
| tree | b188c9c8d577426ed0f8b89e98e7af2acff2619c /docs/ref/models/fields.txt | |
| parent | 84927e110e813c3bea6a600e4474eb577e15f2b9 (diff) | |
[4.2.x] Fixed #34242 -- Doc'd that primary key is set to None when deleting objects.
Backport of 5cd1385356d4b275133ddb0f8c78b2f37c5901eb from main
Diffstat (limited to 'docs/ref/models/fields.txt')
| -rw-r--r-- | docs/ref/models/fields.txt | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt index 4fb39fde82..8d75280a54 100644 --- 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`` ---------- |