Yeah that seems like the option Ill go with since it is probably the most
clean and future compatible. My user's dont need to log into django admin
anyways so that should suffice. Thanks everyone for the feedback!

Cheers,
Dana


On Mon, Aug 3, 2009 at 4:23 PM, Malcolm Tredinnick <malc...@pointy-stick.com
> wrote:

>
> On Mon, 2009-08-03 at 13:13 -0700, Dana wrote:
> > Ok, I understand the login part but what about registration? Wouldn't
> > the user's need a username still? Or am I misunderstanding... And what
> > about Django admin, it would still need a username correct?
>
> Nothing stops you from creating a random string to populate the username
> field with. It has to contain a unique identifier and it's often useful
> if that is actually identifiable -- perhaps created from an amalgam of
> the user's first and last names or something -- but it could be entirely
> random, providing it is unique.
>
> So when you are registering the user, just create a username string
> however you like. The user themselves doesn't have to know or care what
> it is. The thing is, their username won't change, their email address
> might (one of the many small problems with email addresses as unique and
> unchanging identifiers).
>
> Regards,
> Malcolm
>
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to