id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
36755	Example snippet for `models.RESTRICT` should be simplified.	Mads H		"Reading the example snippet for [https://docs.djangoproject.com/en/5.2/ref/models/fields/#django.db.models.RESTRICT `django.db.models.RESTRICT`], I had to go over the snippet a few times to understand what was going on.

{{{#!python
>>> artist_one = Artist.objects.create(name=""artist one"")
>>> artist_two = Artist.objects.create(name=""artist two"")
>>> album_one = Album.objects.create(artist=artist_one)
>>> album_two = Album.objects.create(artist=artist_two)
>>> song_one = Song.objects.create(artist=artist_one, album=album_one)
>>> song_two = Song.objects.create(artist=artist_one, album=album_two)
>>> album_one.delete()
# Raises RestrictedError.
>>> artist_two.delete()
# Raises RestrictedError.
>>> artist_one.delete()
(4, {'Song': 2, 'Album': 1, 'Artist': 1})

}}}

Why are there multiple artists, albums and songs in this example? They don't impact the example in any meaningful way.

After some testing, I figure this snippet demonstrates the same capabilities of `models.RESTRICT`

{{{#!python
>>> artist = Artist.objects.create(name=""artist one"")
>>> album = Album.objects.create(artist=artist)
>>> song = Song.objects.create(artist=artist, album=album)
>>> album.delete()
# Raises RestrictedError.
>>> artist.delete()
(4, {""Album"": 1, ""Artist"": 1, ""Song"": 1})
}}}

Sorry if this is a bit much for such a simple change, but the github checklist explicitly states anything but a typo fix needs a trac ID."	Cleanup/optimization	new	Documentation	5.2	Normal				Unreviewed	0	0	0	0	1	0