blocks|key|334219|text|User模型试图创建两个具有相同名称的字段，一个用于将该User作为target的GameClaims，另一个用于将该User作为claimer的GameClaims。这是Django的docs+on+related_name，它允许您设置属性的名称，以便自动生成的属性不会发生冲突。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|334220|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/dev/topics/db/models/#be-careful-with-related-name-and-related-query-name^0|0|4|S|4|Y|6|15|A|1N|4|1T|7|21|A|2T|C|2L|K|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]|$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@$9|14|A|15|1|16]]|E|$]]|$1|F|3|-4|5|6|7|17|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

The <code>User</code> model is trying to create two fields with the same name, one for the <code>GameClaims</code> that have that <code>User</code> as the <code>target</code>, and another for the <code>GameClaims</code> that have that <code>User</code> as the <code>claimer</code>. Here's the <a href="https://docs.djangoproject.com/en/dev/topics/db/models/#be-careful-with-related-name-and-related-query-name" rel="nofollow noreferrer">docs on <code>related_name</code></a>, which is Django's way of letting you set the names of the attributes so the autogenerated ones don't conflict.

blocks|key|336717|text|您对User有两个外键。Django会自动创建一个从用户到GameClaim的反向关系，通常是gameclaim_set。但是，因为您有两个FK，所以您将有两个gameclaim_set属性，这显然是不可能的。因此，您需要告诉Django使用哪个名称来表示反向关系。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|336718|在FK定义中使用related_name属性。例如：|336719|class+GameClaim(models.Model):
++++target+=+models.ForeignKey(User,+related_name='gameclaim_targets')
++++claimer+=+models.ForeignKey(User,+related_name='gameclaim_users')
++++isAccepted+=+models.BooleanField()|code-block|syntax|javascript|336720|entityMap^0|1B|D|28|D|0|8|C|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]|$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@$9|U|A|V|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|W|8|@]|D|@]|E|$K|L]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

You have two foreign keys to User. Django automatically creates a reverse relation from User back to GameClaim, which is usually <code>gameclaim_set</code>. However, because you have two FKs, you would have two <code>gameclaim_set</code> attributes, which is obviously impossible. So you need to tell Django what name to use for the reverse relation.

Use the <code>related_name</code> attribute in the FK definition. e.g.

<pre><code>class GameClaim(models.Model):
 target = models.ForeignKey(User, related_name='gameclaim_targets')
 claimer = models.ForeignKey(User, related_name='gameclaim_users')
 isAccepted = models.BooleanField()
</code></pre>

blocks|key|334240|text|该操作没有使用抽象基类...但如果你这样做了，你会发现在FK中硬编码related_name+(例如，related_name="myname")会导致许多这样的冲突错误-从基类继承的每个类都会产生一个冲突错误。下面提供的链接包含变通方法，它很简单，但绝对不明显。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334241|从django文档..。|334242|334243|如果在ForeignKey或ManyToManyField上使用related_name属性，则必须始终为该字段指定唯一的反向名称。这通常会在抽象基类中引起问题，因为该类上的字段包含在每个子类中，每次的属性值(包括related_name)都完全相同。|blockquote|334244|334245|334246|更多信息here。|offset|length|334247|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.djangoproject.com/en/dev/topics/db/models/#be-careful-with-related-name-and-related-query-name^0|0|0|0|0|0|0|4|4|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|Y|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|10|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@$L|12|M|13|1|14]]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

The OP isn't using a abstract base class... but if you are, you will find that hard coding the related_name in the FK (e.g. ..., related_name="myname") will result in a number of these conflict errors - one for each inherited class from the base class. The link provided below contains the workaround, which is simple, but definitely not obvious. 

From the django docs...

<blockquote>
 If you are using the related_name
 attribute on a ForeignKey or
 ManyToManyField, you must always
 specify a unique reverse name for the
 field. This would normally cause a
 problem in abstract base classes,
 since the fields on this class are
 included into each of the child
 classes, with exactly the same values
 for the attributes (including
 related_name) each time.
</blockquote>

More info <a href="https://docs.djangoproject.com/en/dev/topics/db/models/#be-careful-with-related-name-and-related-query-name" rel="nofollow noreferrer">here</a>.

blocks|key|3101311|text|当我将一个子模块作为应用程序添加到django项目中时，我似乎偶尔会遇到这种情况，例如，给定以下结构：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3101312|myapp/
myapp/module/
myapp/module/models.py|code-block|syntax|javascript|3101313|如果我将以下内容添加到INSTALLED_APPS：|3101314|'myapp',
'myapp.module',|3101315|Django似乎处理了两次myapp.mymodule+models.py文件，并抛出了上面的错误。这可以通过在INSTALLED_APPS列表中不包括主模块来解决：|3101316|'myapp.module',|3101317|包含myapp而不是myapp.module会导致使用不正确的名称创建所有数据库表，因此这似乎是正确的方法。|offset|length|style|CODE|3101318|我在寻找这个问题的解决方案时偶然发现了这篇文章，所以我想我把这篇文章放在这里:)|3101319|entityMap^0|0|0|0|0|0|0|2|5|A|C|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|14|8|@$Q|15|R|16|S|T]|$Q|17|R|18|S|T]]|9|@]|A|$]]|$1|U|3|V|5|6|7|19|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|X|$]]

I seem to come across this occasionally when I add a submodule as an application to a django project, for example given the following structure:

<pre><code>myapp/
myapp/module/
myapp/module/models.py
</code></pre>

If I add the following to INSTALLED_APPS:

<pre><code>'myapp',
'myapp.module',
</code></pre>

Django seems to process the myapp.mymodule models.py file twice and throws the above error. This can be resolved by not including the main module in the INSTALLED_APPS list:

<pre><code>'myapp.module',
</code></pre>

Including the <code>myapp</code> instead of <code>myapp.module</code> causes all the database tables to be created with incorrect names, so this seems to be the correct way to do it.

I came across this post while looking for a solution to this problem so figured I'd put this here :)

blocks|key|334276|text|只是补充一下乔丹的答案(感谢乔丹的提示)，如果你导入应用程序上面的级别，然后导入应用程序，也可能会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334277|myproject/+++++apps/+++++++++foo_app/+++++++++bar_app/|offset|length|style|CODE|334278|因此，如果你正在导入应用程序，foo_app和bar_app，那么你可能会遇到这个问题。我的应用程序、foo_app和bar_app都列在settings.INSTALLED_APPS中|334279|而且您无论如何都要避免导入应用程序，因为这样您就会在两个不同的命名空间中安装相同的应用程序|334280|apps.foo_app和foo_app|334281|entityMap^0|0|0|1I|0|0|0|0|C|D|7|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@$D|W|E|X|F|G]|$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|O|$]]

Just adding to Jordan's answer (thanks for the tip Jordan) it can also happen if you import the level above the apps and then import the apps e.g.

<code>myproject/
 apps/
 foo_app/
 bar_app/</code>

So if you are importing apps, foo_app and bar_app then you could get this issue. I had apps, foo_app and bar_app all listed in settings.INSTALLED_APPS

And you want to avoid importing apps anyway, because then you have the same app installed in 2 different namespaces

<code>apps.foo_app</code>
and
<code>foo_app</code>

blocks|key|339212|text|有时，您必须在related_name中使用额外的格式-实际上，在使用继承的任何时候。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|339213|class+Value(models.Model):
++++value+=+models.DecimalField(decimal_places=2,+max_digits=5)
++++animal+=+models.ForeignKey(
++++++++Animal,+related_name="%25(app_label)s_%25(class)s_related")

++++class+Meta:
++++++++abstract+=+True

class+Height(Value):
++++pass

class+Weigth(Value):
++++pass

class+Length(Value):
++++pass|code-block|syntax|javascript|339214|这里没有冲突，但是related_name只定义了一次，并且Django将负责创建唯一的关系名称。|339215|然后，在Value类的子类中，您将可以访问：|339216|herdboard_height_related
herdboard_lenght_related
herdboard_weight_related|339217|entityMap^0|7|C|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|V|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|W|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|X|8|@]|D|@]|E|$]]|$1|O|3|P|5|H|7|Y|8|@]|D|@]|E|$I|J]]|$1|Q|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|R|$]]

Sometimes you have to use extra formatting in <code>related_name</code>
- actually, any time when inheritance is used.

<pre><code>class Value(models.Model):
 value = models.DecimalField(decimal_places=2, max_digits=5)
 animal = models.ForeignKey(
 Animal, related_name="%(app_label)s_%(class)s_related")

 class Meta:
 abstract = True

class Height(Value):
 pass

class Weigth(Value):
 pass

class Length(Value):
 pass
</code></pre>

No clash here, but related_name is defined once and Django will take care for creating unique relation names.

then in children of Value class, you'll have access to:

<pre><code>herdboard_height_related
herdboard_lenght_related
herdboard_weight_related
</code></pre>

I want to create an object that contains 2 links to Users. For example:

<pre><code>class GameClaim(models.Model):
 target = models.ForeignKey(User)
 claimer = models.ForeignKey(User)
 isAccepted = models.BooleanField()
</code></pre>

but I am getting the following errors when running the server:

<ul>
<li><blockquote>
 Accessor for field 'target' clashes with related field 'User.gameclaim_set'. Add a related_name argument to the definition for 'target'.
</blockquote></li>
<li><blockquote>
 Accessor for field 'claimer' clashes with related field 'User.gameclaim_set'. Add a related_name argument to the definition for 'claimer'.
</blockquote></li>
</ul>

Can you please explain why I am getting the errors and how to fix them?

Django: Why do some model fields clash with each other?

数据库

服务器

Django

我想创建一个包含2个用户链接的对象。例如：class GameClaim(models.Model):    target = models.ForeignKey(User)    claimer = models.ForeignKey(User)    isAccepted = models.BooleanField...

问Django:为什么一些模型字段会相互冲突？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django:为什么一些模型字段会相互冲突？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Django:为什么一些模型字段会相互冲突？
EN