What are Independent Associations and Foreign Key Associations? [duplicate]

by

Just my opinions about WHY to use independent or foreign key associations:

Independent associations

Pros:

  • This is correct way to go in object oriented world. In object oriented world we are using references inside our aggregates, not some magic keys.

Cons:

  • With pure POCO you don’t know if principal relation is really NULL or just not loaded because in both cases your reference is null. You must ask context to differ between those two nulls. This was not a problem with heavy EntityObject base entities where every navigation property to principal entity was paired with another property suffixed Reference providing some additional details about the relation.
  • EF’s way to manage independent associations is quite complex especially when it comes to attaching detached object graphs. Each independent association has its own state and it can never be in Modified state. Every modification always consists of setting old relation as deleted and creating new relation as added – this is a real mess when you try to use it.
  • It was reported that independent associations slow down view generation during EF’s initialization (or during view pregeneration) significantly.
  • Independent association can be much harder to use in data-binding scenarios where you need to bind just foreign key.

Foreign key associations

Pros:

  • Simple. Key properties are easy to manage and they solve all issues with independent associations – no state for foreign associations, direct data-binding, immediate visibility if relation exists (key is not null), etc.

Cons:

  • They are conceptually wrong and offering them in EF was a big step back from object world to relational world. I still believe that correct solution was improving or changing the way how independent associations are handled even if it could cause huge breaking changes between EFv1 and EFv4. I also don’t like current situation where we have two types of associations with completely different behavior. There should be only one type with well defined behavior and optional foreign key properties exposed on entity.

This difference matters only for one-to-many associations because one-to-one are always Foreign key associations and many-to-many are always independent associations.

More Related Contents:

  1. Entity Framework Join 3 Tables
  2. Entity Framework 4 – AddObject vs Attach
  3. Entity Framework Timeouts
  4. EF Including Other Entities (Generic Repository pattern)
  5. Entity Framework 4 Delete Object from entity collection
  6. Entity Framework/Linq EXpression converting from string to int
  7. Why does the Contains() operator degrade Entity Framework’s performance so dramatically?
  8. Non-static method requires a target
  9. Creating Composite Key Entity Framework
  10. Adding stored procedures complex types in Entity Framework
  11. The result of a query cannot be enumerated more than once
  12. Entity Framework/Linq to SQL: Skip & Take
  13. The object cannot be deleted because it was not found in the ObjectStateManager
  14. A dependent property in a ReferentialConstraint is mapped to a store-generated column
  15. Entity Framework – Add Navigation Property Manually
  16. Calculated column in EF Code First
  17. Entity Framework – Invalid Column Name ‘*_ID”
  18. EF5 Code First – Changing A Column Type With Migrations
  19. Entity Framework Include() is not working
  20. Better way to query a page of data and get total count in entity framework 4.1?
  21. EF4 Code First: how to add a relationship without adding a navigation property
  22. Entity Framework 4: How to find the primary key?
  23. How to Refresh DbContext
  24. Add the where clause dynamically in Entity Framework
  25. Is it possible to prevent EntityFramework 4 from overwriting customized properties?
  26. Entity Framework Code First naming conventions – back to plural table names?
  27. LINQ to Entities group-by failure using .date
  28. Repository Pattern, POCO, and Business Entities
  29. Modelling polymorphic associations database-first vs code-first
  30. Using Include in Entity Framework 4 with lambda expressions

Leave a Comment