Configure inheritance by using the O/R Designer
The Object Relational Designer (O/R Designer) supports the concept of single-table inheritance as it is often implemented in relational systems. In single-table inheritance, there is a single database table that contains fields for both parent information and child information. With relational data, a discriminator column contains the value that determines which class any record belongs to.
For example, consider a Persons table that contains everyone employed by a company. Some people are employees and some people are managers. The Persons table contains a column named EmployeeType that has a value of 1 for managers and a value of 2 for employees; this is the discriminator column. In this scenario, you can create a subclass of employees and populate the class with only records that have an EmployeeType value of 2. You can also remove columns that do not apply from each of the classes.
Creating an object model that uses inheritance (and corresponds to relational data) can be somewhat confusing. The following procedure outlines the steps required for configuring inheritance with the O/R Designer. Following generic steps without referring to an existing table and columns might be difficult, so a walkthrough that uses data is provided. For detailed step-by-step directions for configuring inheritance by using the O/R Designer, see Walkthrough: Creating LINQ to SQL classes by using single-table inheritance (O/R Designer).
To create inherited data classes
Open the O/R Designer by adding a LINQ to SQL Classes item to an existing Visual Basic or C# project.
Drag the table you want to use as the base class onto the O/R Designer.
Drag a second copy of the table onto the O/R Designer and rename it. This is the derived class, or subclass.
Click Inheritance in the Object Relational Designer tab of the Toolbox, and then select the subclass (the table you renamed) and connect it to the base class.
Note
Click the Inheritance item in the Toolbox and release the mouse button, click the second copy of the class you created in step 3, and then select the first class you created in step 2. The arrow on the inheritance line points to the first class.
In each class, delete any object properties that you do not want to appear and that are not used for associations. You receive an error if you attempt to delete object properties used for associations:
The property <property name> cannot be deleted because it is participating in the association <association name>.Note
Because a derived class inherits the properties defined in its base class, the same columns cannot be defined in each class. (Columns are implemented as properties.) You can enable the creation of columns in the derived class by setting the inheritance modifier on the property in the base class. For more information, see Inheritance basics (Visual Basic).
Select the inheritance line in the O/R Designer.
In the Properties window, set the Discriminator Property to the column name that distinguishes the records in your classes.
Set the Derived Class Discriminator Value property to the value in the database that designates the record as the inherited type. (This is the value that is stored in the discriminator column and is used to designate the inherited class.)
Set the Base Class Discriminator Value property to the value that designates the record as a base type. (This is the value that is stored in the discriminator column and is used to designate the base class.)
Optionally, you can also set the Inheritance Default property to designate a type in an inheritance hierarchy that is used when loading rows that do not match any defined inheritance code. In other words, if a record has a value in its discriminator column that does not match the value in either the Derived Class Discriminator Value or Base Class Discriminator Value properties, the record loads into the type designated as the Inheritance Default.