Entity Framework Pitfalls Index

Updated on January 16th

These are the posts on Entity Framework pitfalls I’ve written so far. This post will be updated whenever there are more.

Starting with #29 I will also be covering Entity Framework Core.

1. Validation Does Not Load Lazy Properties

2. Concrete Table Inheritance and Identity Keys

3. Cannot Return Complex Types From SQL Queries

4. Non Nullable Columns in Table Per Class Hierarchy Inheritance

5. Deleting Detached Entities With Required References

6. Null Navigation Properties

7. Deleting Orphans

8. Date/Time Operations

9. Batch Modifications

10. Registering Custom Database Functions for LINQ

11. Collections of Types Other Than ICollection<T> Are Ignored

12. String Length Validation

13. Non Public Entity Sets Setter

14. Mapping Discriminator Columns

15. Command Interceptors and Identity Keys

16. Table Valued Functions

17. Lazy Loading and Proxy Creation

18. Using Stored Procedures for Basic Operations

19. DbConfiguration Classes Are Automatically Loaded

20. Composite Primary Keys

21. TransactionScope

22. Cascade Deletes

23. Attaching New Entities With Existing Related Ones

24. Entity Refresh

25. Migrations and DbContext Construction

26. Queries Over Navigation Properties When There Are Foreign Key Properties Are Ignored

27. Null Semantics

28. Skip/Take Position Matters

29. No TransactionScope Support (EF Core)