Django报错 HINT: Add or change a related_name argument to the definition for 'GodownentryReturn.suppl

最新推荐文章于 2024-07-17 00:01:04 发布
最新推荐文章于 2024-07-17 00:01:04 发布
阅读量8.8k 收藏 4
点赞数 2
分类专栏： python基础 文章标签： django报错
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/m0_37156322/article/details/86691765
版权

Unhandled exception in thread started by <function wrapper at 0x05569030>
Traceback (most recent call last):
File “G:\workspace\pycharm\carwin\carwin_env\lib\site-packages\django\utils\autoreload.py”, line 226, in wrapper
fn(*args, **kwargs)
File “G:\workspace\pycharm\carwin\carwin_env\lib\site-packages\django\core\management\commands\runserver.py”, line 116, in inner_run
self.check(display_num_errors=True)
File “G:\workspace\pycharm\carwin\carwin_env\lib\site-packages\django\core\management\base.py”, line 472, in check
raise SystemCheckError(msg)
django.core.management.base.SystemCheckError: SystemCheckError: System check identified some issues:

ERRORS:
article.GodownentryReturn.supplier: (fields.E304) Reverse accessor for ‘GodownentryReturn.supplier’ clashes with reverse accessor for ‘GodownentryReturn.supplier’.
HINT: Add or change a related_name argument to the definition for ‘GodownentryReturn.supplier’ or ‘GodownentryReturn.supplier’.
part.GodownentryReturn.supplier: (fields.E304) Reverse accessor for ‘GodownentryReturn.supplier’ clashes with reverse accessor for ‘GodownentryReturn.supplier’.
HINT: Add or change a related_name argument to the definition for ‘GodownentryReturn.supplier’ or ‘GodownentryReturn.supplier’.

原因：因为在一个表中多次引用某个外键表，而且没有指定唯一的releated_name，而导致的。
解决方案：将同一个表中外键，增加不同的releated_name。

再观沧海
关注
  • 2
    点赞
  • 踩
  • 4
    收藏
    觉得还不错? 一键收藏
  • 1
    评论
专栏目录
Django使用详解:ORM 的反向查找(related_name)
12-25
先定义两个模型，一个是A，一个是B，是一对多的类型。 class A(models.Model): name= models.CharField('名称', max_length=32) class B(models.Model): a= models.ForeignKey(A, verbose_name='A\u7c7b',related_name = "test") name = models.CharField('称呼', max_length=16) 如果我们要查询一个A拥有哪些B的话，那我们要怎么做呢 通过主表来查询子表 A.objects.get(id=A_id).test
一个模型中有两个外键指向同一张表时，创建迁移模型时报错：“ HINT: Add or change a related_name argument to the definition for 'Ans...
weixin_30571465的博客
08-23 442
class AnswersModel(models.Model): author = models.ForeignKey(FrontUserModel,null=True,related_name='answers_user') …… relay_to = models.ForeignKey(FrontUserModel,null=True,related_name='relay_to...
Django开发问题汇总
IThdq的博客
03-23 1536
Django开发问题汇总 1.NewUser继承AbstractUser出现错误： HINT: Add or change a related_name argument to the definition for 'NewUser.user_permissions' or 'User.user_permissions' 解决方案：在settings.py中加入申明AUTHUSE
Django学习0 -- 问题汇总
Rolei的博客
11-03 2020
Django学习0 -- 学习问题汇总
python 用户认证模型类数据迁移报错
weixin_41061575的博客
05-26 1468
python 用户认证模型类数据迁移报错如下： auth.User.groups: (fields.E304) Reverse accessor for 'User.groups' clashes with reverse accessor for 'User.groups'. HINT: Add or change a related_name argument to the definition for 'User.groups' or 'User.groups'. auth.User...
Django:HINT: Add or change a related_name argument to the definition for ‘x.person_1‘ or ‘x.person‘.
单林敏的博客
04-14 2716
想了很多天，想到使用model添加很多备用的Person数据，如下 class Project(models.Model): name = models.CharField(max_length=100) video = models.ForeignKey(Video, on_delete=models.CASCADE, null=True) person = models.ForeignKey(Person, null=True, blank=True, on_delete=mod
Django自定义用户模型类
Qycccccc的博客
10-14 1152
django.core.management.base.SystemCheckError: SystemCheckError: System check identified some issues: ERRORS: auth.User.groups: (fields.E304) Reverse accessor for ‘auth.User.groups’ clashes with reverse accessor for ‘users.User.groups’. HINT: Add or change
django报错：add_atr() takes 0 positional arguments but 1 was given
12-22
TypeError at /add_atr/ add_atr() takes 0 positional arguments but 1 was given Request Method: GET Request URL: http://127.0.0.1:8000/add_stu/ Django Version: 3.0.3 Exception Type: TypeError Exception ...
Django外键（ForeignKey）操作以及related_name的作用详解
09-18
本篇将详细讲解Django外键操作及related_name的作用。 首先，理解外键（ForeignKey）的基本概念。在数据库设计中，外键是一个字段，它的值引用另一个表的主键，这样可以建立起不同表之间的关联。在Django中，我们...
django orm 通过related_name反向查询的方法
09-19
在Django ORM（对象关系映射）中，`related_name` 是一个非常有用的特性，它允许我们在模型间建立反向关系查询。这个特性主要用于当一个模型通过外键关联到另一个模型时，从被关联模型的角度定义一个反向访问的名称...
django扩展AbstractUser创建两张用户表，用于维护两种对象，比如一方是卖家，一方是买家。报错，已解决
loveyanga的博客
11-22 1443
首先，老样子对于django的AbstractUser的基础上进行扩展，扩展出了两张表。一张是AUser表，一张是BUser表。 但是这个时候发现在创建的时候，看到了满屏的错误，如下： NO1002.AUser.groups: (fields.E304) Reverse accessor for 'AUser.groups' clashes with reverse accessor for ...
【新人填坑024】django2.0报user.User.groups: (fields.E304) Reverse accessor for 'User.groups' clashes with r
weixin_43521165的博客
06-01 976
报错原文： user.User.groups: (fields.E304) Reverse accessor for 'User.groups' clashes with reverse accessor for 'User.groups'. HINT: Add or change a related_name argument to the definition for '...
django Error: HINT: Add or change a related_name argument to the definition for 'UserProfile.groups'...
weixin_30438813的博客
10-08 694
# 解决方案： 因自己重新封装user为UserProfile故在 settings中 添加自己的 转载于:https://www.cnblogs.com/LYliangying/p/9752505.html
解决报错HINT: Add or change a related_name argument to the definition for ‘users.User.user_permissions‘
最新发布
我的个人博客
07-17 479
看到这样的提示时，通常意味着在你的项目中存在两个模型（或多个）都有相同名称的反向关系（reverse relation），这导致 Django 在内部处理这些关系时产生冲突。在你的情况下，冲突发生在。将AUTH_USER_MODEL = "auth.User"复制到dev.py（settings.py）配置文件中，并将auth改为users。，你需要在你的 settings.py 文件中设置。模型并且继承了 Django 的。上，这通常是因为你自定义了。），但同时又保留了默认的。
related_name
xiaobukasi的专栏
08-05 257
related_name必须是唯一的不然可能会报错： Add or change a related_name argument to the definition for
django的数据库模型中的域多次引用同一个外键（表）
davidsu33的专栏
07-08 9653
执行python manage makemigrations OnlineUpgrade时，报如下错误： D:\KLServer\pycode\KLServer>python manage.py makemigrations OnlineUpgrade SystemCheckError: System check identified some issues: ERRORS: OnlineU
django 设置指向自己的多对多关系，且要增加额外字段而需自定义关系表，执行py manage.py makemigrations时报fields.E304 错误 .related_name
qq_27361945的博客
10-25 1060
 原始代码： # 邻区多对多关系表 class ZJadjacent(models.Model): cellfrom = models.ForeignKey(ZJcell, on_delete=models.CASCADE) cellto = models.ForeignKey(ZJcell, on_delete=models.CASCADE) # 两个邻区间的距离 ...
HINT: Add or change a related_name argument to the definition for 'User.user_permissions' or 'User.u
gymaisyl的博客
12-20 5697
在settings.py中添加写一段代码 AUTH_USER_MODEL = 'users.User' 即可
WARNINGS: ?: (staticfiles.W004) The directory 'static' in the STATICFILES_DIRS setting does not exist. buy.Cart: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the BuyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.d b.models.BigAutoField'. buy.Orders: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the BuyConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django.d b.models.BigAutoField'. sale.Brand: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the SaleConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django. db.models.BigAutoField'. sale.Carinfo: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the SaleConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'django. db.models.BigAutoField'. userinfo.UserInfo: (models.W042) Auto-created primary key used when not defining a primary key type, by default 'django.db.models.AutoField'. HINT: Configure the DEFAULT_AUTO_FIELD setting or the UserinfoConfig.default_auto_field attribute to point to a subclass of AutoField, e.g. 'dja ngo.db.models.BigAutoField'. No changes detected
06-02
The warnings indicate the following issues: - `staticfiles.W004`: The `STATICFILES_DIRS` setting is configured to use a directory named `static`, but it does not exist in your project. You should either create the directory or modify the setting to use an existing directory. - `models.W042`: Auto-created primary keys are being used for several of your models (`buy.Cart`, `buy.Orders`, `sale.Brand`, `sale.Carinfo`, `userinfo.UserInfo`). You should explicitly define a primary key field for each model instead of relying on the default auto-generated primary key. To do this, add a `primary_key=True` argument to a field in the model definition, or specify a custom primary key field using the `primary_key` attribute. - `No changes detected`: This is not a warning, but rather an informational message indicating that no changes were detected in your models that require migration. To address the `models.W042` warnings, you can either add a `primary_key=True` argument to an existing field or create a new field with the `primary_key=True` argument. For example: ```python class Cart(models.Model): cart_id = models.AutoField(primary_key=True) # ... ``` Alternatively, you can configure the `DEFAULT_AUTO_FIELD` setting in your project settings to specify a custom primary key field for all models in your project. For example: ```python # settings.py from django.conf import settings class BuyConfig(AppConfig): default_auto_field = 'django.db.models.BigAutoField' settings.configure(BUY_CONFIG=BuyConfig) ``` This will set the default auto-generated primary key field for all models in the `buy` app to `BigAutoField`. You can repeat this pattern for other apps in your project as well.
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值