django.contrib.auth.models.AbstractBaseUser.last_login should allow null=True
|Reported by:||veena||Owned by:||anonymous|
|Cc:||simon@…, martin.paquette@…||Triage Stage:||Someday/Maybe|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
I think attribute last_login in model User in django.contrib.auth should has property null=True.
Now it has only default=datetime.datetime.now
So, when you create new user the last_login is set to now datetime.
But when you create new user it doesn't mean that user has been logged in. For example in django-registration there is first user created and link to activation is sended to his email. After user activates his account he can login.
Change History (10)
comment:1 Changed 6 years ago by Simon Greenhill
- Triage Stage changed from Unreviewed to Design decision needed
comment:5 Changed 3 years ago by SmileyChris
- Easy pickings unset
- Triage Stage changed from Design decision needed to Someday/Maybe
comment:7 Changed 10 months ago by mohitbagga
- Owner changed from nobody to anonymous
- Status changed from new to assigned
comment:8 Changed 9 months ago by timo
- Keywords schemamigration added; auth last login user removed
- Summary changed from Last_login in django.contrib.auth should has null=True to django.contrib.auth.models.AbstractBaseUser.last_login should allow null=True
- Type changed from Bug to Cleanup/optimization