Entity Framework: One Database, Multiple DbContexts. Is this a bad idea? [closed]

by

You can have multiple contexts for single database. It can be useful for example if your database contains multiple database schemas and you want to handle each of them as separate self contained area.

The problem is when you want to use code first to create your database – only single context in your application can do that. The trick for this is usually one additional context containing all your entities which is used only for database creation. Your real application contexts containing only subsets of your entities must have database initializer set to null.

There are other issues you will see when using multiple context types – for example shared entity types and their passing from one context to another, etc. Generally it is possible, it can make your design much cleaner and separate different functional areas but it has its costs in additional complexity.

More Related Contents:

  1. DbSet.Find method ridiculously slow compared to .SingleOrDefault on ID
  2. Can anyone spot why I keep getting this error testing the EF 5 beta
  3. Code-first vs Model/Database-first [closed]
  4. The entity type is not part of the model for the current context
  5. EntityFramework code-first custom connection string and migrations
  6. Improve navigation property names when reverse engineering a database
  7. How do I detach objects in Entity Framework Code First?
  8. Entity Framework code first unique column
  9. EF5 Code First Enums and Lookup Tables
  10. Debug code-first Entity Framework migration codes
  11. Order navigation properties when using Include and/or Select methods with EF 4.1 Code-First?
  12. Entity framework code-first null foreign key
  13. Entity Framework loading child collection with sort order
  14. How do I singularize my tables in EF Code First?
  15. Set decimal(16, 3) for a column in Code First Approach in EF4.3 [duplicate]
  16. How to create index in Entity Framework 6.2 with code first
  17. How do you ensure Cascade Delete is enabled on a table relationship in EF Code first?
  18. Entity Framework and calling context.dispose()
  19. What is the syntax for self referencing foreign keys in EF Code First?
  20. How to create index in Entity Framework 6.2 with fluent configuration
  21. EF Code First DBContext and Transactions
  22. Entity Framework Code First : Setting up One-To-One foreign key association using Annotations
  23. What is the best practice in EF Core for using parallel async calls with an Injected DbContext?
  24. Mixing Fluent API and DataAnnotations in EF code first
  25. EF Code First foreign key without navigation property
  26. DbContext AutoDetectChangesEnabled set to false detecting changes
  27. Entity Framework Code First Using Guid as Identity with another Identity Column
  28. LINQ To Entities + Include + Anonymous type issue
  29. Why does EF5 code first use datetime2 when inserting a nullable datetime into the database?
  30. Entity framework code first delete with cascade

Leave a Comment