Warning: file_get_contents(/data/phpspider/zhask/data//catemap/2/python/280.json): failed to open stream: No such file or directory in /data/phpspider/zhask/libs/function.php on line 167

Warning: Invalid argument supplied for foreach() in /data/phpspider/zhask/libs/tag.function.php on line 1116

Notice: Undefined index: in /data/phpspider/zhask/libs/function.php on line 180

Warning: array_chunk() expects parameter 1 to be array, null given in /data/phpspider/zhask/libs/function.php on line 181
Python Django自定义身份验证模型注册表单返回唯一用户名错误_Python_Django_Django Models_Web Applications_Django Views - Fatal编程技术网

Python Django自定义身份验证模型注册表单返回唯一用户名错误

Python Django自定义身份验证模型注册表单返回唯一用户名错误,python,django,django-models,web-applications,django-views,Python,Django,Django Models,Web Applications,Django Views,我有自己的用户模型user。我有一个用户注册表,它在下面返回此错误: duplicate key value violates unique constraint "users_user_username_06e46fe6_uniq" DETAIL: Key (username)=() already exists. 可能是用户模型被保存了两次吗 这是我的表格: class FighterSignUpForm(UserCreationForm): class Meta(Use

我有自己的用户模型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
子类化,不如从
AbstractBaseUser
子类化。因为
AbstractUser
默认有
username
字段及其唯一性,但是
AbstractBaseUser
只有
password
last\u login
字段,它提供了用户模型的核心实现。还有一个缺点,比如,
AbstractBaseUser
没有
is_staff
名字
姓氏
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')
请查看有关使用自定义用户模型的详细信息。您还可以检查AbstractBaseUserAbstractUser之间的差异

您仍然可以使用
AbstractUser
,但需要覆盖
用户名
字段

class User(AbstractBaseUser, PermissionsMixin):
     username = models.CharField(_('username'), max_length=255, blank=True, unique=False)
...
# rest of your fields

可能是您的模型中没有定义名为“username”的字段吗?然后为字段设置空值,并点击“唯一约束”。@sergey感谢您的回复。你认为你可以提供一个例子或详细说明这一点吗?非常感谢