Changing the type of an (Entity Framework) entity that is part of an inheritance hierarchy

by

One of the tenets of OOP is that instances cannot change their type. Think: Can you do this with ordinary .NET objects? Of course not. You can’t do an end run around this hard and fast rule by persisting them with the EF, either.

Adding a row to the DB doesn’t change an instance’s type, either; it just lies to the EF about what you saved. In the relational domain, you’re adding a relation, not changing an object’s class, because the relational domain doesn’t know about objects.

So the long and the short of this is that using the EF doesn’t change the .NET rule that instances cannot change their type.

What should you do when you need to do this, then? Well, think about how this works in your problem domain. An employee is a person. Their employment status is related to the person, but their status is not actually the person.

Use composition instead of inheritance. I would probably model this as Person, with a collection of Employment instances. As a person’s employment situation changes, you can assign stop/termination dates to the old records, and add new records for new jobs.

I happened to read this blog post this morning, which may be further food for thought.

Edited to add If you do work around this by implementing a DB stored procedure, make sure nobody is actually using the system at the time when you execute it. Because this is completely illegal in .NET object space, the Entity Framework presumes that it cannot happen. If you circumvent the Entity Framework and do it, and a user happens to have a live ObjectContext at the time, then this ObjectContext will be out of sync with the database in a way that the normal optimistic concurrency protections in the Entity Framework did not detect. You won’t corrupt data, but the user with the active ObjectContext may see some incredibly strange errors.

More Related Contents:

  1. Introducing FOREIGN KEY constraint may cause cycles or multiple cascade paths – why?
  2. LINQ to Entities does not recognize the method
  3. How do you effectively model inheritance in a database?
  4. Like Operator in Entity Framework?
  5. How can I query for null values in entity framework?
  6. .NET Entity Framework and transactions
  7. Get Database Table Name from Entity Framework MetaData
  8. Can you use Microsoft Entity Framework with Oracle? [closed]
  9. “Items collection must be empty before using ItemsSource.”
  10. Undo changes in entity framework entities
  11. Update primary key value using entity framework
  12. ASP.NET MVC: Is Controller created for every request?
  13. EF LINQ include multiple and nested entities
  14. Is is possible to check if an object is already attached to a data context in Entity Framework?
  15. Generate POCO classes in different project to the project with Entity Framework model
  16. How to work with Enums in Entity Framework?
  17. What are Navigation Properties in Entity Framework for?
  18. LINQ to Entities does not recognize the method Int32 get_Item(Int32)
  19. How to set default value for POCO’s in EF CF?
  20. How to map table splitting in EF Code First?
  21. Organizationally, where should I put common queries when using Entity Framework Code First?
  22. Entity Framework 4 Single() vs First() vs FirstOrDefault()
  23. Using entity framework on multiple databases
  24. entity framework Unable to load the specified metadata resource [duplicate]
  25. The model backing the ‘ApplicationDbContext’ context has changed since the database was created
  26. Entity Framework Find vs. Where
  27. Do you think it’s advantageous to switch to Entity Framework? [closed]
  28. ‘ObjectContext’ vs ‘DbContext’ in Entity Framework
  29. Using Entity Framework entities as business objects?
  30. Entity framework 4.3 run migrations at application start

Leave a Comment