Entity Developer supports three hierarchy types for managing inheritance relationships. On the diagram, inheritance relationships are represented as solid line connections with white arrows.
In Table Per Hierarchy inheritance, all hierarchy classes are mapped to the same table, containing columns for all the properties of the hierarchy and additional discriminator columns that distinguish objects of one class from another.
When creating a Table Per Hierarchy hierarchy from an autogenerated database model:
In Table Per Type inheritance, each hierarchy class is mapped to one table. Every table provides additional details that describe a new type based on another table, which is that table’s parent.
In Table Per Concrete Type inheritance, each non-abstract hierarchy class is mapped to one table.
To establish this relationship in a model autogenerated from a database:
To create an inheritance, use one of these methods:
button on the Model toolbar or Model Explorer toolbar.The Inheritance Editor dialog opens, where you can:

Note
The Discriminator options are available only for Table Per Hierarchy (TPH) inheritance.