> Can the username be Null?
>From the help text on username attr:
"Required. 30 characters or fewer. Alphanumeric characters only
(letters, digits and underscores)."
> What if it was 1,000,000 names, like if I was publishing a phone book?
Then using the user model, which does keep track of a
My first question would be: Are you absolutely certain that none of
those 1000 other people will ever need a login?
Basically, if any of those users would ever need to be promoted to
login status, the User model is your best bet. As Samuel mentioned,
just set "is_active" to False and probably
Want more info ?
Create a profile model and tie it to the user in settings.py:
AUTH_PROFILE_MODULE = 'profile.UserProfile'
Then you can use
user.get_profile().phone_number for example.
http://www.b-list.org/weblog/2006/jun/06/django-tips-extending-user-model/
When i started using Django i
Marty Alchin wrote:
> My first question would be: Are you absolutely certain that none of
> those 1000 other people will ever need a login?
anything is possible.
I would think at some point it isn't a good idea to use the User table. What
if
it was 1,000,000 names, like if I was publishing a
The user table has first/last name. great. I need to manage about 1500
people,
and only 500 will have any need for a site login. So where should I store the
1000 names that don't need to be a user record?
I can think of:
Everyone gets a User record. (given this is the easiest, what
Have the "is_active" field of the User model set to False for the
users that don't need a login.
The auth login will raise an error if an inactive user tries to log
in.
Always try to use what is there.
On Nov 16, 3:02 pm, Carl Karsten <[EMAIL PROTECTED]> wrote:
> The user table has first/last
6 matches
Mail list logo
