![](/img/trans.png)
[英]How to create custom registration form using auth_user model and cutom model fields in django
[英]Django custom auth model registration form returns unique username error
我有自己的用戶模型,稱為 User。 我有一個用戶注冊表,在下面返回此錯誤:
duplicate key value violates unique constraint "users_user_username_06e46fe6_uniq"
DETAIL: Key (username)=() already exists.
可能是用戶模型被保存了兩次?
這是我的表格:
class FighterSignUpForm(UserCreationForm):
class Meta(UserCreationForm.Meta):
model = User
fields = ('first_name', 'last_name','email','password1', 'password2',)
@transaction.atomic
def save(self):
user = super().save(commit=False)
user.is_fighter = True
user.is_active = False
user.save()
return user
這是我的觀點:
class FighterSignUpView(CreateView):
model = User
form_class = FighterSignUpForm
template_name = 'registration/user_signup.html'
def get_context_data(self, **kwargs):
kwargs['user_type'] = 'example'
return super().get_context_data(**kwargs)
def form_valid(self, form):
user = form.save()
這是自定義用戶模型:
class UserManager(BaseUserManager):
use_in_migrations = True
def _create_user(self, email, password, **extra_fields):
if not email:
raise ValueError('The given email must be set')
email = self.normalize_email(email)
user = self.model(email=email, **extra_fields)
user.set_password(password)
user.save(using=self._db)
return user
def create_user(self, email, password=None, **extra_fields):
extra_fields.setdefault('is_staff', False)
extra_fields.setdefault('is_superuser', False)
return self._create_user(email, password, **extra_fields)
def create_superuser(self, email, password, **extra_fields):
extra_fields.setdefault('is_staff', True)
extra_fields.setdefault('is_superuser', True)
if extra_fields.get('is_staff') is not True:
raise ValueError('Superuser must have is_staff=True.')
if extra_fields.get('is_superuser') is not True:
raise ValueError('Superuser must have is_superuser=True.')
return self._create_user(email, password, **extra_fields)
class User(AbstractUser):
email = models.EmailField(_('Email'), unique=True)
USERNAME_FIELD = 'email'
REQUIRED_FIELDS = []
is_type1 = models.BooleanField(default=False, verbose_name="type1")
is_type2 = models.BooleanField(default=False, verbose_name="type2")
is_type3 = models.BooleanField(default=False, verbose_name="type")
is_confirmed = models.BooleanField(default=False, verbose_name="Has Confirmed Email")
objects = UserManager()
我最近剛剛從 SQlite3 移動了我的數據庫,並且在運行前者時沒有遇到過這個問題。
與其從AbstractUser
子類AbstractUser
,我認為從AbstractBaseUser
子類化更好。 因為AbstractUser
默認有username
字段並且是唯一的,而AbstractBaseUser
只有password
和last_login
字段,它提供了 User 模型的核心實現。 有不好的一面,以及像, AbstarctBaseUser
沒有is_staff
, first_name
, last_name
, is_superuser
領域和權限相關領域的缺失,以及。 所以,如果你像這樣使用它會更好:
class User(AbstractBaseUser, PermissionsMixin):
first_name = models.CharField(_('first name'), max_length=255, blank=True)
last_name = models.CharField(_('last name'), max_length=255, blank=True)
email = models.EmailField(_('email address'), blank=True, max_length=50)
is_staff = models.BooleanField(_('staff status'), default=False,
help_text=_('Designates whether the user'
' can log into this admin '
'site.'))
is_active = models.BooleanField(_('active'), default=True,
help_text=_('Designates whether '
'this user should be '
' treated as '
'active. Unselect this '
' instead of '
' deleting accounts.'))
objects = UserManager()
# rest of your fields
USERNAME_FIELD = 'email'
REQUIRED_FIELDS = ['email']
def get_short_name(self):
return self.first_name
class Meta:
verbose_name = _('user')
verbose_name_plural = _('users')
請在此處查看有關使用自定義用戶模型的更多詳細信息。 您也可以檢查這個SO answer關於AbstractBaseUser和AbstractUser之間的差異。
或者你仍然可以使用AbstractUser
但需要覆蓋username
段
class User(AbstractBaseUser, PermissionsMixin):
username = models.CharField(_('username'), max_length=255, blank=True, unique=False)
...
# rest of your fields
聲明:本站的技術帖子網頁,遵循CC BY-SA 4.0協議,如果您需要轉載,請注明本站網址或者原文地址。任何問題請咨詢:yoyou2525@163.com.