Django使用auth_user表在关系中

发布于 2025-02-06 05:07:08 字数 2596 浏览 1 评论 0原文

我想在一对多和多一对一的关系中使用auth_user表。

  • 这是个坏主意吗?
  • 我可以做吗?
  • 我该怎么做?

一切都通过管理员发生。因此,我只需要模型。

我让它起作用...

class Profile(models.Model):
    profile_name = models.CharField(max_length=100)
    profile_url = models.URLField(max_length=255)
    def __str__(self):
        return self.profile_name  
 

class Teacher(AbstractUser):
    profile = models.ManyToManyField(Profile, through='TeacherProfile')
    def __str__(self):
        return self.email

class TeacherProfile(models.Model):
    teacher = models.ForeignKey(Teacher, on_delete=models.CASCADE)
    profile = models.ForeignKey(Profile, on_delete=models.CASCADE)
    profile_url = models.URLField(max_length=255)
    class Meta:
        unique_together = (('teacher', 'profile'),)
    def __str__(self):
        return f'{self.teacher}, {self.profile}' 

desc vcm_teacher;

+--------------+--------------+------+-----+---------+----------------+
| Field        | Type         | Null | Key | Default | Extra          |
+--------------+--------------+------+-----+---------+----------------+
| id           | bigint(20)   | NO   | PRI | NULL    | auto_increment |
| password     | varchar(128) | NO   |     | NULL    |                |
| last_login   | datetime(6)  | YES  |     | NULL    |                |
| is_superuser | tinyint(1)   | NO   |     | NULL    |                |
| username     | varchar(150) | NO   | UNI | NULL    |                |
| first_name   | varchar(150) | NO   |     | NULL    |                |
| last_name    | varchar(150) | NO   |     | NULL    |                |
| email        | varchar(254) | NO   |     | NULL    |                |
| is_staff     | tinyint(1)   | NO   |     | NULL    |                |
| is_active    | tinyint(1)   | NO   |     | NULL    |                |
| date_joined  | datetime(6)  | NO   |     | NULL    |                |
+--------------+--------------+------+-----+---------+----------------+

我必须在设置中添加此行。py

AUTH_USER_MODEL = 'vcm.Teacher'
drop database vcm;
create database vcm;

find . -path "*/migrations/*.py" -not -name "__init__.py" -delete
find . -path "*/migrations/*.pyc"  -delete

python3 manage.py makemigrations
python3 manage.py migrate
python3 manage.py createsuperuser

这里有一些信息如何扩展Django用户模型

I'd like to use the auth_user table in one-to-many and many-to-many relationships.

  • Is this a bad idea?
  • Can I do it?
  • How do I do it?

Everything is happening through Admin. So, I just need the models.

I got it working...

class Profile(models.Model):
    profile_name = models.CharField(max_length=100)
    profile_url = models.URLField(max_length=255)
    def __str__(self):
        return self.profile_name  
 

class Teacher(AbstractUser):
    profile = models.ManyToManyField(Profile, through='TeacherProfile')
    def __str__(self):
        return self.email

class TeacherProfile(models.Model):
    teacher = models.ForeignKey(Teacher, on_delete=models.CASCADE)
    profile = models.ForeignKey(Profile, on_delete=models.CASCADE)
    profile_url = models.URLField(max_length=255)
    class Meta:
        unique_together = (('teacher', 'profile'),)
    def __str__(self):
        return f'{self.teacher}, {self.profile}' 

desc vcm_teacher;

+--------------+--------------+------+-----+---------+----------------+
| Field        | Type         | Null | Key | Default | Extra          |
+--------------+--------------+------+-----+---------+----------------+
| id           | bigint(20)   | NO   | PRI | NULL    | auto_increment |
| password     | varchar(128) | NO   |     | NULL    |                |
| last_login   | datetime(6)  | YES  |     | NULL    |                |
| is_superuser | tinyint(1)   | NO   |     | NULL    |                |
| username     | varchar(150) | NO   | UNI | NULL    |                |
| first_name   | varchar(150) | NO   |     | NULL    |                |
| last_name    | varchar(150) | NO   |     | NULL    |                |
| email        | varchar(254) | NO   |     | NULL    |                |
| is_staff     | tinyint(1)   | NO   |     | NULL    |                |
| is_active    | tinyint(1)   | NO   |     | NULL    |                |
| date_joined  | datetime(6)  | NO   |     | NULL    |                |
+--------------+--------------+------+-----+---------+----------------+

I had to add this line in settings.py

AUTH_USER_MODEL = 'vcm.Teacher'
drop database vcm;
create database vcm;

find . -path "*/migrations/*.py" -not -name "__init__.py" -delete
find . -path "*/migrations/*.pyc"  -delete

python3 manage.py makemigrations
python3 manage.py migrate
python3 manage.py createsuperuser

There's some info here How to Extend Django User Model

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文