How to use interface properties with CodeFirst

by

An imperfect solution is to just merge these interfaces you want to persist into base classes and break down the underlying objects with subclasses. EF does support this, and if you go with Table Per Hierarchy (the default), you can sort all of the underlying subclassed objects by a shared property using a regular LINQ query from EF instead of having to get crafty and do things like write raw SQL or get multiple lists into memory and sort the union without the help of the DB, like you would with Cel’s solution of interfaces and adapters.

You could also take the child/parent types of interfaces as generics, so that when the implementer uses concrete classes in the Db they can mostly use your interfaces, but tell EF to use concrete classes:

public interface IParent<out TChild>
    where TChild : IChild
{
    ICollection<TChild> Children { get; set; }

Someone could create their Db classes like:

public class Parent : IParent<Child>
. . .

But still use them like:

IParent<IChild> parents = db.Parents.Include(p => p.Children).ToArray();

Because the generic is marked out, the generic is covariant and therefore can take anything that meets the generic’s restrictions, including the above cast up the type tree to the IChild interface.

That said, if you really want to persist interfaces, the right answer is probably to use NHibernate:
How to map an interface in nhibernate?

And some coders recommend you keep interfaces on entities in any ORM limited to a few shared properties, or risk misuse:
Programming to interfaces while mapping with Fluent NHibernate

More Related Contents:

  1. EF Core Second level ThenInclude missworks
  2. The relationship could not be changed because one or more of the foreign-key properties is non-nullable
  3. Entity Framework – Why explicitly set entity state to modified?
  4. Convert value when mapping
  5. Disable lazy loading by default in Entity Framework 4
  6. Best way to check if object exists in Entity Framework? [closed]
  7. How to select top N rows for each group in a Entity Framework GroupBy with EF 3.1
  8. EF5 Code First Enums and Lookup Tables
  9. Entity Framework 4.1 DbContext Override SaveChanges to Audit Property Change
  10. Entity Framework One-To-One Mapping Issues
  11. How can I delete 1,000 rows with EF6?
  12. Entity Framework 4 selective lazy loading properties
  13. When should I call SaveChanges() when creating 1000’s of Entity Framework objects? (like during an import)
  14. Adding Validation Attributes With an Entity Framework Data Model
  15. How to exclude one table from automatic code first migrations in the Entity Framework?
  16. Ramifications of DbSet.Create versus new Entity()
  17. Entity Framework : How do you refresh the model when the db changes?
  18. Entity framework code first creates “discriminator” column
  19. EF Migrations: Rollback last applied migration?
  20. Using EF Core ThenInclude() on Junction tables
  21. How can I disable migration in Entity Framework 6.0
  22. How to update not every fields of an object using Entity Framework and EntityState.Modified
  23. What is the best practice in EF Core for using parallel async calls with an Injected DbContext?
  24. Many to Many Relationships not saving
  25. What goes into DbContextOptions when invoking a new DbContext?
  26. Metadata file not found – Data.Entity.Model
  27. What is the best way to compare two entity framework entities?
  28. Why does EF5 code first use datetime2 when inserting a nullable datetime into the database?
  29. EF4 LINQ Ordering Parent and all child collections with Eager Loading (.Include())
  30. EF5 How to get list of navigation properties for a domain object

Leave a Comment