On Jan 14, 2010, at 2:44 AM, nameless wrote:
> I want to use "id" as identifier for each user. So every user will
> have an url like this:
>
> http://www.example.com/827362
>
> I don't want username for my project.
> So, if I can't delete it, I think to insert email in username field
> and I
On Jan 14, 8:12 pm, Alexander Dutton wrote:
> On 14/01/10 09:51, nameless wrote:> I am asking whether is a good solution to
> having 2 fields with the
> > same value ( username and email ) because both are required.
> > Or is there another solution ?
>
> This depends on
I want to use "id" as identifier for each user. So every user will
have an url like this:
http://www.example.com/827362
I don't want username for my project.
So, if I can't delete it, I think to insert email in username field
and I don't want another identifier in username field as random
On 14/01/10 09:51, nameless wrote:
> I am asking whether is a good solution to having 2 fields with the
> same value ( username and email ) because both are required.
> Or is there another solution ?
>
This depends on whether you don't want distinct usernames hanging
around, or you simply want
I am asking whether is a good solution to having 2 fields with the
same value ( username and email ) because both are required.
Or is there another solution ?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
I want a Registration Form with only email + password. I am thinking
to insert automatically email in username field. So, for eash user, I
will have this:
username: exam...@example.com
password: mypassword
email: exam...@example.com
Of course email + password will be used in login process.
6 matches
Mail list logo