do you mean that you want someone to be able to have a duplicate
username as long as they are at a different company ?
if so, why ? maybe that requirement should just be worked around.
but there is certainly a way to do it without hacking User.
-f;lix
On Jul 7, 4:58 pm, brydon <[EMAIL PROTECTED]> wrote:
> Ok, no responses.....let's try this another way....
>
> Is there a way to swap out the model class that represents User?
> brydon
>
> On Jul 4, 3:24 pm, brydon <[EMAIL PROTECTED]> wrote:
>
> > Hey,
>
> > I'm assuming I can always fork auth and modify the User class
> > directly, however, I'd prefer to avoid that.
>
> > I'd like to add a new model class called Company. Data and users
> > within a company are mutually exclusive. I'd therefore like to allow
> > usernames to be unique in the context of a Company.
>
> > If I hacked auth.User then I'd be doing something like...
>
> > unique_together = (("username", "company"),)
>
> > For now, the user's company is available through their profile,
> > User.get_profile().company.
>
> > Any thoughts how to accomplish this without forking auth??
>
> > thanks,
> > brydon
--~--~---------~--~----~------------~-------~--~----~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
