按外键搜索(Search by foreign key)

 如果从数据库设计的角度考虑这个问题，那么拥有一个具有以下参数的BaseballPlayer对象可能会很奇怪： 
 
 
 
 球队 
 
 
 位置 
 
 
 对手 
 
 
 大约10或11个统计数据（历史） 
 
 
 约10或11个统计数据（预计） 
 
 
 投手对决 
 
 
 天气 
 
 
 因为某些特定的东西与特定的BaseballPlayer保持相对固定，例如名称等，但这些其他东西是流动的和短暂的。 
 
 如果您将其设计为具有各种数据库表的应用程序，那么，此处列出的每个事物都可能代表一个单独的表，并且BaseballPlayer与这些其他表的关系相当于当前和以前的Team等。 
 
 因此，我可能会将问题分解为更多的类，包括StatsClass和Team类（这可能是Opponent真正的......）。 
 
 但这一切都取决于你想做什么。 通常当您向后弯曲以将数据塞入结构或执行相同操作以将其取回时，可以重新设计设计以使您的工作更轻松。 

If you think about this from the perspective of database design, it would probably be odd to have a BaseballPlayer object that has the following parameters:
 
 
 
Team 
 
 
Position 
 
 
Opponent 
 
 
about 10 or 11 stats (historical) 
 
 
about 10 or 11 stats (projected) 
 
 
pitcher matchup 
 
 
weather
 
 
Because there are certain things associated with a particular BaseballPlayer which remain relatively fixed, such as name, etc., but these other things are fluid and transitory.
 
If you were designing this as an application with various database tables, then, it's possible that each of the things listed here would represent a separate table, and the BaseballPlayer's relationship with these other tables amount to current and former Team, etc.
 
Thus, I would probably break up the problem into more classes, including a StatsClass and a Team class (which is probably what an Opponent really is...).
 
But it all depends what you would like to do. Usually when you are bending over backwards to cram data into a structure or doing the same to get it back out, the design could be reworked to make your job easier.