Maps an inheritance hierarchy in a LINQ to SQL application.
Assembly: System.Data.Linq (in System.Data.Linq.dll)
Thetype exposes the following members.
|Equals||Infrastructure. Returns a value that indicates whether this instance is equal to a specified object. (Inherited from Attribute.)|
|Finalize||Allows an object to try to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.)|
|GetHashCode||Returns the hash code for this instance. (Inherited from Attribute.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|Match||When overridden in a derived class, returns a value that indicates whether this instance equals a specified object. (Inherited from Attribute.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|ToString||Returns a string that represents the current object. (Inherited from Object.)|
One is specified per mapped class.
Note the following when you map inheritance hierarchies:
All classes in a hierarchy must be mapped to a single table.
The table for an inheritance hierarchy must be declared on the mapped type that is at the top of the hierarchy. You cannot specify the table or mapping attributes in a class that is derived from the top class.
You can use an interface in a hierarchy, but LINQ does not map it.
You can skip a class in the hierarchy when you map classes, but you can query against mapped classes only.
For correct materialization, discriminator code values must be unique and match the values in the database. A row with a discriminator code value that does not exactly match (even by casing) instantiates the class by using IsDefault set to true.
For a list of the operating systems and browsers that are supported by Silverlight, see Supported Operating Systems and Browsers.