The additional foreignkey back to user is designated users who have
permission to edit the profiles of only their  subordinates. These owners
are non staff
On Mar 18, 2016 3:49 PM, "Avery Laird" <[email protected]> wrote:

> Hi Matt,
>
> It might be useful if you explain what you're trying to do. For example,
> why do you need the foreign key relationship back to auth.User? I'm having
> trouble imagining a situation where you'd need both a OneToOne relationship
> and a ForeignKey relationship to the same model. Maybe you can accomplish
> your task a different way.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to