ER图关系模型：步转换算法.docVIP

3.2.3?Mapping from ER Models to Relational Models  HYPERLINK /content/SSD/SSD7/1.5.1/normal/pg-dbdesign/pg-ermodels/pg-ermapping/ \l mapping-algo Mapping Algorithm  HYPERLINK /content/SSD/SSD7/1.5.1/normal/pg-dbdesign/pg-ermodels/pg-ermapping/ \l Example Example There is almost a one-to-one correspondence between the ER constructs and the relational ones. The two major distinctions are: In a relational schema, relationships are represented implicitly through primary and foreign keys of participating entities. In a relational schema, columns of relations cannot be multi-valued or composite. Composite attributes are replaced with their simple component ones, and multi-valued attributes are stored in a separate relation. ER ConstructRelational Constructentitytable1:1 or 1:N relationshipForeign key (or a table to capture the relationship)M:N relationshiprelationship table and 2 foreign keysn-ary relationship typerelationship table and n foreign keyssimple attributecolumncomposite attributeset of simple component columnsmulti-valued attributetable and foreign keyvalue setdomainkey attributeprimary (or secondary) key? Mapping Algorithm We can translate an ER schema to a relational schema by following a nine-step algorithm based on the one given in Elmasri and Navathe 1994. The algorithm attempts to minimize the need for joins and NULL values when defining relations (Steps 2, 4, and 5). For each strong entity E: Create a new table. Include as its columns, all the simple attributes and simple components of the composite attributes of E. Identify the primary key and the alternate keys. Do not include any multi-valued attribute as a key. If the only unique field of an entity is a multi-valued attribute, introduce an artificial primary key field. For each weak entity W that is associated with only one 1:1 identifying owner relationship: Identify the table T of the owner entity type. Include as columns of T, all the simple attrib