On Feb 20, 6:07 am, Beres Botond wrote:
> To be honest I don't really see why you would need multiple user
> profile models,
> instead of having one user profile model, and each entry would define
> a different
> user profile.
What do you mean by "one user profile model, and each entry would
def
To be honest I don't really see why you would need multiple user
profile models,
instead of having one user profile model, and each entry would define
a different
user profile.
Of course I don't know the full details/requirementes of your project,
and what exactly you are
trying to do ... but I c
On Feb 19, 6:39 pm, Andrew Ingram wrote:
> Simplest solution : don't worry about the AUTH_PROFILE_MODULE setting.
>
> I'm working on a site with numerous modules that contain user account
> information, such as orders and newsletter preferences. I just have a
> foreignkey to the auth User on each
On Thu, 2009-02-19 at 14:53 -0800, Gok Mop wrote:
> I'm struggling with how to design something, and I'm pretty sure
> somebody has an easy solution.
>
> I need to store different information about different classes of
> users. I want to attach those classes as the user profile to my
> django.co
Simplest solution : don't worry about the AUTH_PROFILE_MODULE setting.
I'm working on a site with numerous modules that contain user account
information, such as orders and newsletter preferences. I just have a
foreignkey to the auth User on each of these, eg:
class OrderAccount(models.Model):
I'm struggling with how to design something, and I'm pretty sure
somebody has an easy solution.
I need to store different information about different classes of
users. I want to attach those classes as the user profile to my
django.contrib.auth.User object, so I can always cross-walk from the
Us
6 matches
Mail list logo
