Closed dwasyl closed 2 years ago
One motivator for using a separate model is that this is a separate relationship to model and not just an "attribute" of the organization.
A more urgent reason, if memory serves correctly, is the cyclic relationship in the database between the organization and organization users table. This does work! But I think Django's migrations didn't handle this before (???).
Hi all,
Just had a question for regular maintainers/users of
django-organization
regardingOrganizationOwner
s. If the relationship is onl ya single owner perOrganization
, is it necessary to have a separate object for the owner relationship? Would anowner
field (as a FK to aOrganizationUser
) onOrganization
not accomplish roughly the same thing?Just getting my head around the structure so appreciate any thoughts!
Cheers