Proposal for User/Member structure

[giobber]

Objective

Make login available with multiple user emails and username

Structure

class User(AbstractBaseUser):
    username = models.CharField(max_length=40, unique=True)
    is_active = models.BooleanField(default=True)
    is_admin = models.BooleanField(default=False)
    password = ...

    USERNAME_FIELD = "username"

    objects = UserManager()
    @property
    def email(self):
         return self.emails.filter(primary=True).first()

class UserEmail(Model):
    email = EmailField(unique=True)
    user = ForeignKey(User)
    primary = BoolUniqueForUser()  # Mail used for communications

# Inside membership module
from django.conf import settings
from django.contrib.auth import get_user_model

class Member:
    ...
    user = OneToOneField(settings.AUTH_USER_MODEL)
    ...

Reference

• Useful article: link
• documentation: link

What to do to avoid CircularDependencyError error on migrations

link to documentation

• Create new auth app inside admin (require models.py, admin.py, 'migrationsandapps.py`
• Create custom user, without any difference with default user
• link that user to auth_user table
• Connect new app in settings by:
  • adding App class in apps.py with name admin.auth
  • adding admin.auth.apps.AuthApp to settings.INSTALLED_APPS
• migrate
• make required changes to User class and migrate it

If this not work (and probably will) take a breath, remove all migrations for user and memberships and start anew (fortunately we are still in alpha), the other models migrations will live fine

[giobber]

After a more careful analysis (with collaboration of @ZompaSenior) we decide to not support multiple mail access

• A custom user need to be created
• username will be removed
• email field will be the substitute for username
• during migration of our data email will be chosen as the last email used to register a membership
• an additional table for "additional email" could be added later if really needed but it's better to solve this outside new site