I already created ticket for this http://code.djangoproject.com/ticket/7220
veena
On 14 pro, 23:59, Sergiy Kuzmenko wrote:
> I wonder if there is a particular reason why last_login field of is not
> defined as "null=True"? It makes sense to me to have it as null which would
> mean that the user
> However, the bigger issue is that I think changing the definition of
> this field really requires a migration mechanism (which would update
> existing databases), which we don't have. We really don't want the
> situation of bugs which are impossible to reproduce because they
> depend on installat
On Tuesday 15 December 2009 23:10:23 Matt Schinckel wrote:
> I came across one today:
> contrib.auth.tokens.PasswordResetTokenGenerator
> has a method _make_token_with_timestamp, which uses last_login to
> create the
> token. This means that if someone generates a password reset
> request, the t
On Dec 15, 8:59 am, Sergiy Kuzmenko wrote:
> I wonder if there is a particular reason why last_login field of is not
> defined as "null=True"? It makes sense to me to have it as null which would
> mean that the user never logged in. Could there be any dependencies relying
> on this field not bein
On Dec 15, 8:59 am, Sergiy Kuzmenko wrote:
> I wonder if there is a particular reason why last_login field of is not
> defined as "null=True"? It makes sense to me to have it as null which would
> mean that the user never logged in. Could there be any dependencies relying
> on this field not bein
I wonder if there is a particular reason why last_login field of is not
defined as "null=True"? It makes sense to me to have it as null which would
mean that the user never logged in. Could there be any dependencies relying
on this field not being null?
Thanks
Sergiy
--
You received this messag
