From fa52bb77747be33dc9dfb07c26307e60958adaaa Mon Sep 17 00:00:00 2001
From: noFFENSE <orazkhanmansur@gmail.com>
Date: Wed, 18 Jan 2023 16:56:24 +0600
Subject: [4.2.x] Fixed #34242 -- Doc'd that primary key is set to None when
 deleting objects.

Backport of 5cd1385356d4b275133ddb0f8c78b2f37c5901eb from main
---
 docs/ref/models/fields.txt | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'docs/ref/models/fields.txt')

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``
 ----------
 
-- 
cgit v1.3