Profile model is great when we need to add information, but it becomes woefully unhelpful if we want to change or remove information. I am not a fan of the fact that our current implementation uses both a
username and an
User model. If we want to use only the
User model itself.
User model is actually a very thin model that inherits from
AbstractUser, where most of the user fields are defined. However, this class in turn inherits from
AbstractBaseUser defines the heart of the
User model, supplying the
last_login field as well as the methods to interact with the
password field. The
PermissionsMixin defines ...