Personally I think get_profile() is an anti-pattern, just access it
like any other OneToOneField (and that's what you want... not
unique=True on a ForeignKey). Just set up a models.OneToOneField(User,
related_name=XXX), then you can access the profile as user.XXX. The
User model and all of its asso
I'm reading up on extending the user model and planing out a project
and wanted to clarify a point.
I want to have a single user list to authenticate using the standard
user model.
I want then to create multiple apps in the project, each with roles
and permissions tied to the user defined in the us
2 matches
Mail list logo