在这种情况下，什么是适当的模型来减少逻辑?-Whatisthepropermodeltoreducelogicinthissituation?

1  

Id go with the first model and use select_related() to avoid the extra db calls.

Id使用第一个模型，并使用select_related()避免额外的db调用。

1  

If you're looking to reduce redundancy and maintain consistiency of logic...

如果你想减少冗余并保持逻辑的一致性……

Match: - id
- name

匹配:- id - name

Match_Player: (2 records per match)
- match_id
- player_id
- is_home

Match_Player:(每场2条记录)- match_id - player_id - is_home

Match_Player_Score:
- match_id
- player_id
- score

Match_Player_Score: - match_id - player_id - score

0  

I'd avoid having redundant data in the database. This leaves open the possibility of the database data getting internally inconsistent and messing up everything.

我将避免数据库中存在冗余数据。这会导致数据库数据在内部变得不一致并导致一切混乱。

Use a single entry per match, as in your second example. If you plan ahead, you can accomplish the two sets of logic pretty easily. Take a look at proxy models. There might be an elegant way to do this -- have all of your logic refer to the data fields through accessors like get_my_score and get_opponent_score. Then build a Proxy Model class which swaps home and away.

每个匹配使用一个条目，如第二个示例中所示。如果你提前计划，你可以很容易地完成这两套逻辑。看看代理模型。有一种很好的方法可以做到这一点——让您的所有逻辑通过诸如get_my_score和get_defaulent_score这样的访问器引用数据字段。然后，构建一个代理模型类，该类交换了home和away。

class match(models.Model):

    def get_my_score(self):
        return self.home_player_score

    def get_opponent_score(self):
        return self.away_player_score

    def did_i_win(self):
        return self.get_my_score() > self.get_opponent_score()


class home_player_match(match):
    class Meta:
        proxy = True

    def get_my_score(self):
        return self.away_player_score

    def get_opponent_score(self):
        return self.home_player_score

Or maybe you want two Proxy models, and have the names in the base model class be neutral. The problem with this approach is that I don't know how to convert a class from one proxy model to another without reloading from the database. You want a "rebless" as in perl. You could do this by using containment rather than inheritance. Or maybe just a flag in the wrapper class (not stored in the database) saying whether or not to swap fields. But I'd recommend some solution like that -- solve the tricky stuff in code and don't let the database get inconsistent.

或者，您可能需要两个代理模型，并让基模型类中的名称保持中立。这种方法的问题是，我不知道如何在不重新加载数据库的情况下将一个类从一个代理模型转换到另一个代理模型。您需要像在perl中那样使用“rebless”。您可以通过使用容器而不是继承来实现这一点。或者可能只是包装器类中的一个标志(不是存储在数据库中)，说明是否交换字段。但我还是建议一些类似的解决方案——解决代码中的棘手问题，不要让数据库变得不一致。