Table Inheritance in Entity Framework

In OOP, we use inheritance to reduce unnecessary code. We can also archive inheritance in Entity Framework. Entity Framework supports three different types of inheritance.
  1. THP - Table Per Hierarchy
  2. TPT - Table Per Type
  3. TPC - Table Per Concrete Class

Table Per Hierarchy

Table-per-hierarchy inheritance uses one database table to maintain data for more than one entity types in an inheritance hierarchy in Entity Framework. In other words, there are many entity sets in EF for a single database table. In TPH, the base table or entity could be created and it has a number of derived entities (must be more than one) that are inherited from the base table.

Inheritance using TPH

Define entity set in Conceptual Model that will act as a base entity type and others act as derived types. A derived entity type must inherit from a base type and in the conceptual model set Base Type Attribute. The conceptual model defines only non-inherited properties for derived types. The discriminator column (which acts as a separator for base type) is mapped as part of a condition in the Mapping Model, so there can be no corresponding property on any entity types in the hierarchy. The exception to this rule is when the condition uses an Is Null or Is Not Null comparison. In this case, the discriminator column can have a corresponding property on an entity type if the discriminator column contains more than a value like an integer then the column must be nullable or have a default value to ensure that when the new type is created and saved to the database, the column has some values. Conditions must be used to map each derived type and base type in the hierarchy. There is no mapping or conditions allowed if the base type is abstract. The Base Entity type and derived entity are mapped in the "EntitySetMapping" element in Mapping Model. IsTypeOf keyword is used to set the value of the Type Name attribute on derived types. Use a mapping condition to discriminate between types in the hierarchy.
Here are the steps to follow.
Step 1: Create an Entity Model from the database.
Step 2: Add new Entity (right-click on Entity designer Add -go to Entity).
Entity1.jpg
Step 3: Make derived Entity Like "AdminDepartment" and "Sales Department".
Entity2.jpg
Entity3.jpg
Step 4: Remove discriminator columns from the base type Table "Department".
Step 5: Add Table mapping - right-click on Derived type entity and select "Table Mapping".
Entity4.jpg
Entity5.jpg
Step 6: Map Table and add a condition.
Step 7: Make a Base Entity abstract.
Entity6.jpg
Step 8: Now update EDMX manually.
  1. Storage Model -In the storage Model, Define the Entity Type, Key, and properties that are the same as the database. There is no definition for derived in the storage model.
    Coding
    1. <EntityType Name="Departments">
    2. <Key>
    3. <PropertyRef Name="DepartmentId" />
    4. </Key>
    5. <Property Name="DepartmentId" Type="int" Nullable="false" />
    6. <Property Name="DepartmentCode" Type="varchar" Nullable="false" MaxLength="25" />
    7. <Property Name="DepartmentName" Type="varchar" Nullable="false" MaxLength="100" />
    8. <Property Name="IsActive" Type="bit" Nullable="false" />
    9. <Property Name="DepartmentType" Type="int" Nullable="false" />
    10. </EntityType>
  2. Conceptual Model- In the conceptual Model, define the base entity without the discriminator column and also define a derived type.
    Coding
    1. <EntityType Name="Department" Abstract="true">
    2. <Key>
    3. <PropertyRef Name="DepartmentId" />
    4. </Key>
    5. <Property Type="Int32" Name="DepartmentId" Nullable="false" />
    6. <Property Type="String" Name="DepartmentCode" Nullable="false" MaxLength="25" FixedLength="false" Unicode="false" />
    7. <Property Type="String" Name="DepartmentName" Nullable="false" MaxLength="100" FixedLength="false" Unicode="false" />
    8. <Property Type="Boolean" Name="IsActive" Nullable="false" />
    9. <NavigationProperty Name="Employees" Relationship="AdventureWorksModel.FK_Employees_Department" FromRole="Department" ToRole="Employee" />
    10. </EntityType>
    11. <EntityType Name="SalesDepartment" BaseType="AdventureWorksModel.Department">
    12. </EntityType>
  3. Mapping Model- the Mapping Model contains the entity type mapping i.e. mapping between the conceptual model and storage model.
    Example
    In this example, the mapping between the Department and Sales Department is defined in the same EntitySetMapping. The IsTypeOf keyword is used to indicate the type of entity set (i.e. base entity or derived entity). The Condition tag is a condition in which a sale Department is identified from the Department.
    1. <EntitySetMapping Name="Departments" >
    2. <EntityTypeMapping TypeName="IsTypeOf(AdventureWorksModel.Department)" >
    3. <MappingFragment StoreEntitySet="Departments" >
    4. <ScalarProperty Name="DepartmentId" ColumnName="DepartmentId" />
    5. <ScalarProperty Name="IsActive" ColumnName="IsActive" />
    6. <ScalarProperty Name="DepartmentName" ColumnName="DepartmentName" />
    7. <ScalarProperty Name="DepartmentCode" ColumnName="DepartmentCode" />
    8. </MappingFragment>
    9. </EntityTypeMapping>
    10. <EntityTypeMapping TypeName="IsTypeOf(AdventureWorksModel.SalesDepartment)">
    11. <MappingFragment StoreEntitySet="Departments">
    12. <ScalarProperty Name="DepartmentId" ColumnName="DepartmentId" />
    13. <Condition ColumnName="DepartmentType" Value="2" />
    14. </MappingFragment>
    15. </EntityTypeMapping>
    16. <EntityTypeMapping TypeName="IsTypeOf(AdventureWorksModel.AdminDepartment)">
    17. <MappingFragment StoreEntitySet="Departments">
    18. <ScalarProperty Name="DepartmentId" ColumnName="DepartmentId" />
    19. <Condition ColumnName="DepartmentType" Value="1" />
    20. </MappingFragment>
    21. </EntityTypeMapping>
    22. </EntitySetMapping>
In the next article, we will learn about TPT (Table per Type) and how to add it in EDMX.