(I've just started my first project and I'm already in trouble. I've read the documentation but still haven't .... assimilated it yet. So sorry for the numpty question.)
I'm building an application to organise product demonstration events. It will include a foreign key identifying a member of our sales staff and one for a freelancer. There will be only one staff and freelancer per event. Both user types will need to have access to the system. Both will have different roles and responsibilities. And the staff member will also have additional info, like a budget etc. Is this a good example where the auth.models.User should be extended to have a class for the sales staff and one for a freelancer? By splitting them up it would make the distinction easier for our admin people to add new sales people and freelancers. Alternatively perhaps I should keep it simple. I did try to just have 2x one to many foreign keys to the User model, but because it's going to the same model I had to use "related_name". But this seems so weird having to have link table in the database when this isn't a many to many relationship. Any advice on what approach would be better. ALJ -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
