《从类模型映射到关系模型.docxVIP

根据领域模型分析数据模型Mapping from the Class Model to the Relational Model从类模型映射到关系模型Having described the two domains of interest and the notation to be used, we can now turn our attention as to how to map or translate from one domain to the other. The strategy and sequence presented below is meant to be suggestive rather than proscriptive - adapt the steps and procedures to your personal requirements and environment.在需要对两个领域建模时，现在我们可以关注如何从一个领域映射或转换映射到另一个领域。以下的策略和方法，就是要启发，而不是强制的步骤和程序应用到您的个人需求和环境。1. Model ClassesFirstly we will assume we are engineering a new relational database schema from a class model we have created. This is obviously the easiest direction as the models remain under our control and we can optimise the relational data model to the class model. In the real world it may be that you need to layer a class model on top of a legacy data model - a more difficult situation and one that presents its own challenges. For the current discussion will focus on the first situation. At a minimum, your class model should capture associations, inheritance and aggregation between elements. 1. 类建模首先，我们将假设从已创建的类模型生成一个新的关系数据库模型。这显然是最容易的，可控制的，可以通过关系数据库模型反向优化类模型。在现实世界中可能你需要将类模型作为数据模型的上层，这是更困难的情况，也对自己提出了一个挑战。对于目前的讨论将集中在第一种情况。至少，你的类模型应捕元素之间的联系、继承和聚集关系。2. Identify persistent objectsHaving built our class model we need to separate it into those elements that require persistence and those that do not. For example, if we have designed our application using the Model-View-Controller design pattern, then only classes in the model section would require persistent state. 2. 确认持久对象已建成的类模型，我们需要区分这些元素，那些需要持久化和那些不是。例如，如果我们设计我们的应用程序使用Model - View- Controller设计模式，那么只有MODEL模型部分需要持久化状态。3. Assume each persistent class maps to one relational tableA fairly big assumption, but one that works in most cases (leaving the inheritance issue aside for the moment). In the simplest model a class from the logical model maps to a relational table, either in whole or in part. The logical extension of this is that