From c0128e3a81cfb07238324b185958a88631e94963 Mon Sep 17 00:00:00 2001 From: Carlton Gibson Date: Mon, 16 Sep 2024 22:40:11 +0200 Subject: [PATCH] Fixed #35767 -- Adjusted customizing User model docs. --- docs/topics/auth/customizing.txt | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 3f8be983f8..f41b10fb4a 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -400,10 +400,9 @@ the Django model that you wish to use as your user model. Using a custom user model when starting a project ------------------------------------------------- -If you're starting a new project, it's highly recommended to set up a custom -user model, even if the default :class:`~django.contrib.auth.models.User` model -is sufficient for you. This model behaves identically to the default user -model, but you'll be able to customize it in the future if the need arises:: +If you're starting a new project, you can set up a custom user model that +behaves identically to the default user model by subclassing +:class:`~django.contrib.auth.models.AbstractUser`:: from django.contrib.auth.models import AbstractUser @@ -426,7 +425,7 @@ Changing to a custom user model mid-project ------------------------------------------- Changing :setting:`AUTH_USER_MODEL` after you've created database tables is -significantly more difficult since it affects foreign keys and many-to-many +possible, but can be complex, since it affects foreign keys and many-to-many relationships, for example. This change can't be done automatically and requires manually fixing your