. Net – ORM example using a single table instead of a single table for the entire hierarchy?

From http://blogs.tedneward.com/2006/06/26/The +Vietnam+Of+Computer+Science. Aspx start

"Developers usually take one of two other approaches, with more complex prospects but more efficient in dealing with relational storage: they either work for each specific (most derived) Class creates a table. They prefer to adopt denormalization and its cost. Otherwise, they create a single table in the whole hierarchy. Usually, in any case, they create a discriminator column to indicate the class to which each row in the table belongs (various combinations of these schemes are also possible, but they are usually not created with these two.) Unfortunately, denormalization costs are often important for large amounts of data, and / or tables will contain a large number of empty columns, which will require reducibility constraints on all columns, thus eliminating the powerful integrity constraints provided through RDBMS “

I want to know which ORM uses one way or another, especially those that use a single table and Net?

Solution

I think most leading ORM tools allow different inheritance schemes, including a single table

I can mention DataObjects Net, which only used the class table inheritance scheme in previous versions However, this product has been completely rewritten and now allows three different inheritance schemes: class table, single table and concrete table