I'd like to hear what others think of this approach b/c it makes a lot
of sense to me and does seem much easier in that:
1) The newly defined user object is in request
2) There's one place to get user info
Thanks for sharing,
Rob
--~--~-~--~~~---~--~~
You
put that many to many in UserProfile as per current
django recommendation, and user.get_profile().friends.all() sounds wrong.
With this you can say fuser.friends.get(). Natural.
On 5/8/07, Mi Reflejo <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I have a project with multiple user types.
Hi,
I have a project with multiple user types. That means: Multiple profiles.
Since i don't have one AUTH_PROFILE_MODULE i can't use get_profile(). I
think i could do a intermediate M2M table but i don't want this overload and
i loose user_profile cache (Because in this scenery M2M table
