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 problems could it cause?) 2nd table for the extras. all code that needs to work with the super set will have to work with both tables. (yuck) 2nd table for all people. don't use the name fields in the User table. figure out how to use it to edit a User's Real Name (not the username) in the Admin UI. (This seems best. if you agree, how would I fix the Admin UI?) Thanks, Carl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
