On 5/9/07, Vinay Sajip <[EMAIL PROTECTED]> wrote: > > One simple problem with Amit's approach, as written, is that you have > to deal with "fuser" and "duser", which feels a little kludgy (I > realise he was just demonstrating the concept, but the problem still > remains that you want to think of all the profile information as just > part of the user model. Is the intention just to avoid saying > user.get_profile().xxx? Can't this be done by judiciously overriding > __getattribute__ in User, to delegate to a profile if one is defined?
Agree with you. I was suggesting this solution as a part of multiple type of user scenario, where profile itself would be different. For us, we have endusers, and businesses, and we require different kind of profiles for both of them. .get_profile() does not handle this situation (AFAIK). -- Amit Upadhyay Vakao! +91-9820-295-512 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
